All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Sakib Sajal <sakib.sajal@windriver.com>
Cc: Randy MacLeod <randy.macleod@windriver.com>,
	Trevor Gamblin <trevor.gamblin@windriver.com>,
	Steve Sakoman <steve@sakoman.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Autobuilder data collection for intermittent bugs
Date: Thu, 25 Mar 2021 22:23:29 +0000	[thread overview]
Message-ID: <e2a237d0cc34d56882de9d064287b81858a48a56.camel@linuxfoundation.org> (raw)
In-Reply-To: <768fd8d6-09bb-3e87-fd37-267ac9352866@windriver.com>

Hi Sakib,

On Thu, 2021-03-25 at 18:11 -0400, Sakib Sajal wrote:
> I have been trying, with help from Randy, Trevor and Steve, to run some 
> experiments on an internal autobuilder instance to collect host data 
> during builds for signs of io latency.
> 
> Initially i modified yocto-autobuilder-helper/config.json and added the 
> following 3 lines to existing templates (and created a commit) that were 
> being used so that the builds would start collecting the data.
> 
> 
> +                "BB_HEARTBEAT_EVENT = '5'",
> +                "BB_LOG_HOST_STAT_ON_INTERVAL = '1'",
> +                "BB_LOG_HOST_STAT_CMDS = 'pwd; ls'"
> 
> I also created a template in yocto-autobuilder-helper/config.json
> 
> +        "data-collect" : {
> +            "BUILDINFO" : true,
> +            "BBTARGETS" : "core-image-minimal",
> +            "extravars" : [
> +                "BB_HEARTBEAT_EVENT = '5'",
> +                "BB_LOG_HOST_STAT_ON_INTERVAL = '1'",
> +                "BB_LOG_HOST_STAT_CMDS = 'pwd; ls'"
> +            ]
> +        },
> 
> and modified a builder to use the template:
> 
>          "beaglebone-alt" : {
> -            "MACHINE" : "beaglebone-yocto",
> -            "TEMPLATE" : "altcfg-hw"
> +            "MACHINE" : "qemux86-64",
> +            "TEMPLATE" : "data-collect"
>           },
> 
> Restarted both the controller and the worker, and started the 
> beaglebone-alt build. Once the build started, i checked the conf file in 
> the build directory but those lines were not appended to the local.conf 
> file and hence no log files.

You shouldn't need to restart the controller, the worker should pull and 
use the configuration from the helper branch specified.

I'd note that it writes the config to auto.conf, not local.conf.

It should also give output in the logs about what its doing. For example:

https://autobuilder.yoctoproject.org/typhoon/#/builders/106/builds/2144/steps/10/logs/stdio

is the "Write config" step of beaglebone-alt on the autobuilder where it
clearly says:

Writing /home/pokybuild/yocto-worker/beaglebone-alt/build/build/conf/auto.conf with contents:

What do your logs say?

> In summary, I have been trying to get the 3 lines from the "extravars" 
> above to appear in one of the local.conf files. However none of the 
> builds seems to have been altered.
> 
> I am wondering if the changes that I've made are even being picked up by 
> the controller. Am I missing something?
> 
> Is there an easier way to update the conf files?
> 
> Initially I'd like collect data on a single node and scale it to all the 
> nodes. Any ideas/suggestions are welcome!

What you're doing should work. Its hard to comment more without seeing to logs
but check you're looking at auto.conf.

Cheers,

Richard



  reply	other threads:[~2021-03-25 22:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 22:11 Autobuilder data collection for intermittent bugs Sakib Sajal
2021-03-25 22:23 ` Richard Purdie [this message]
2021-03-26  0:00   ` Randy MacLeod
2021-03-26 17:50     ` Richard Purdie
2021-03-31 21:45       ` Sakib Sajal
2021-03-31 22:01         ` Richard Purdie
2021-04-04 19:56           ` [OE-core] " Randy MacLeod
2021-04-05 14:49             ` Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e2a237d0cc34d56882de9d064287b81858a48a56.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    --cc=sakib.sajal@windriver.com \
    --cc=steve@sakoman.com \
    --cc=trevor.gamblin@windriver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.