From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuild reproduction and generation
Date: Mon, 26 Dec 2016 09:21:27 +0100 [thread overview]
Message-ID: <20161226092127.1c4a40d1@free-electrons.com> (raw)
In-Reply-To: <CADZ=QZ=SU7XthdVfaAQpeY7LKJcsOME1zOusWvZAEjs0OpRfZw@mail.gmail.com>
Hello,
On Mon, 26 Dec 2016 16:15:19 +0800, Yu-Ting Kao wrote:
> I want to contribute some patches for buildroot, and I found autobuild
> <http://autobuild.buildroot.org/>system
> ?that can find bugs at commit early stage.?
>
> 1. How can I run this random build script and send it to autobuild system ?
The script that runs on the autobuilder build machines is available in
the Git repository at https://git.buildroot.org/buildroot-test/, in
scripts/autobuild-run.
In order to submit your build results to autobuild.b.o, you need an
account, which I can create. But before that, you should run the script
standalone for a day or two, look at the generated build results to see
if there isn't anything obviously wrong (i.e not a real build failure,
but a build failure due to your installation).
> 2. How can I reproduce the issue which are posted at autobuild system ?
> All I know is that, copy the config file and build code manually. The
> br-reproduce-build script seems not work normally.
I use the br-reproduce-build script and it works fine for me. Could you
be more specific about the issues you've encountered?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-12-26 8:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 8:15 [Buildroot] Autobuild reproduction and generation Yu-Ting Kao
2016-12-26 8:21 ` Thomas Petazzoni [this message]
2016-12-26 9:07 ` Yu-Ting, Kao
2016-12-26 9:16 ` Thomas Petazzoni
2016-12-26 14:32 ` Yu-Ting, Kao
2016-12-26 14:39 ` Thomas Petazzoni
2016-12-27 1:57 ` Yu-Ting, Kao
2016-12-27 9:45 ` Thomas Petazzoni
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=20161226092127.1c4a40d1@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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