From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Rahul Kumar <rahulk@mvista.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2] bzip2: Add test suite for bzip2
Date: Mon, 27 Apr 2020 19:16:34 +0100 [thread overview]
Message-ID: <543d70c2321008a46e4f21bf84fd3963624e655b.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj_61NP5ZSVHA5UWJN_s86esbc-1nEu2gDdmvMn6AGqRAg@mail.gmail.com>
On Mon, 2020-04-27 at 18:30 +0200, Alexander Kanavin wrote:
> You need to look at configurations defined here:
> http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder-helper/tree/config.json
> and replicate them locally. Then you can reproduce the failures that
> the AB gets in those configurations.
That start of the failing logs on the autobuilder also list out the
configuration options for that build.
Cheers,
Richard
next prev parent reply other threads:[~2020-04-27 18:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 18:39 [PATCH v2] bzip2: Add test suite for bzip2 Rahul Kumar
2020-04-27 15:09 ` [OE-core] " Richard Purdie
2020-04-27 16:25 ` Rahul Kumar
2020-04-27 16:30 ` Alexander Kanavin
2020-04-27 18:16 ` Richard Purdie [this message]
2020-04-27 18:54 ` Rahul Kumar
2020-04-27 19:39 ` Alexander Kanavin
2020-05-01 1:24 ` Randy MacLeod
2020-05-06 11:17 ` Rahul Kumar
[not found] ` <160C6C52084AA802.10857@lists.openembedded.org>
2020-05-12 4:58 ` Rahul Kumar
2020-05-12 23:22 ` Randy MacLeod
2020-05-13 14:28 ` Trevor Gamblin
2020-05-13 18:28 ` Rahul Kumar
2020-05-17 19:17 ` Rahul Kumar
2020-05-17 19:48 ` Peter Kjellerstedt
2020-05-19 11:58 ` Rahul Kumar
2020-05-19 16:29 ` Peter Kjellerstedt
2020-05-19 17:14 ` Rahul Kumar
2020-05-19 21:45 ` Randy MacLeod
2020-05-19 22:10 ` Khem Raj
2020-05-20 0:06 ` Peter Kjellerstedt
2020-05-20 20:56 ` Randy MacLeod
2020-05-25 6:12 ` Rahul Kumar
2020-05-26 17:08 ` Paul Barker
2020-05-12 6:53 ` Peter Kjellerstedt
2020-05-17 23:54 ` Khem Raj
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=543d70c2321008a46e4f21bf84fd3963624e655b.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=rahulk@mvista.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