From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Sakib Sajal <sakib.sajal@windriver.com>,
Randy MacLeod <randy.macleod@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] scripts/oe-timeout-dd-test.sh: add script
Date: Mon, 08 Mar 2021 22:10:00 +0000 [thread overview]
Message-ID: <78d7c30d3d642353fbd52202beb49e1dd74fb7f2.camel@linuxfoundation.org> (raw)
In-Reply-To: <2b197274-5e89-2648-5881-4f2671a1e6aa@windriver.com>
Hi Sakib,
On Mon, 2021-03-08 at 15:46 -0500, Sakib Sajal wrote:
> Randy and I could directly use autobuilders and make the necessary
> changes to run the tests/experiments, if you prefer to do it yourself,
> read on for more details.
I'm happy to have the help. I'm thinking that rather than instrument
one build or a specific test case, we should add something to
yocto-autobuilder-helper on a test branch, that way we can run an
"a-full" or "a-quick" target on the autobuilder under the test and see
if we can get any interesting data.
The autobuilders have a shared output directory we could use to collate
the information, it is exported to the environment as
OEQA_DEBUGGING_SAVED_OUTPUT in config.json in -helper.
I think we therefore need:
a) poky-contrib branch with this change in
b) yocto-autobuilder-helper branch with the config enabled in config.json
c) a further patch to collect up any interesting data and save it to
OEQA_DEBUGGING_SAVED_OUTPUT as a post build event handler for further
analysis. We may be able to patch the existing results collection script
to do this in helper? Obviously the naming of the files on
OEQA_DEBUGGING_SAVED_OUTPUT needs to be multi build safe.
Does that sound like a reasonable approach?
Cheers,
Richard
next prev parent reply other threads:[~2021-03-08 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 20:58 [PATCH] scripts/oe-timeout-dd-test.sh: add script Sakib Sajal
2021-03-08 14:50 ` [OE-core] " Randy MacLeod
2021-03-08 17:33 ` Richard Purdie
2021-03-08 20:46 ` Sakib Sajal
2021-03-08 22:10 ` Richard Purdie [this message]
2021-03-11 20:53 ` Yi Fan Yu
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=78d7c30d3d642353fbd52202beb49e1dd74fb7f2.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
--cc=sakib.sajal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox