From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glmark2: bump version
Date: Tue, 14 Feb 2017 09:44:36 +0100 [thread overview]
Message-ID: <20170214094436.224c3db8@free-electrons.com> (raw)
In-Reply-To: <CAAMH-yt5ar=Y3zRR-Y3XRMSD-nWXGSfOLbY7WMj_+ZUR1+Eb+w@mail.gmail.com>
Hello,
On Tue, 14 Feb 2017 09:27:43 +0100, Gary Bisson wrote:
> > Applied to master, thanks. However, I had to add a reference to an
> > autobuilder issue (after checking that I could reproduce the issue, and
> > that it was indeed fixed by your patch). Next time, could you make sure
> > to include a reference to the autobuilder failure being fixed?
>
> Sure, I didn't know there was an autobuilder issue about it actually.
> I just ran into it myself.
Ah, OK.
> BTW, when we have such case, is it possible to drop the faulty
> defconfig somewhere so the autobuilder can try it later?
Not sure what you mean here. But probably you mean testing a specific
defconfig with all the configurations tested by the autobuilders. Then
if that's what you mean, have a look at support/scripts/test-pkg that
was recently merged. It does exactly that: you provide a config snippet
that enables a selection of packages, and it will build that selection
of packages with all toolchain configurations used by the autobuilders.
> Or is the best option is sending it on the ML or on IRC?
There is no way to "inject" a specific package configuration in the
autobuilders. The autobuilders simply build random selection of
packages, all day long.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-14 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 20:06 [Buildroot] [PATCH] glmark2: bump version Gary Bisson
2017-02-13 21:39 ` Thomas Petazzoni
2017-02-14 8:27 ` Gary Bisson
2017-02-14 8:44 ` Thomas Petazzoni [this message]
2017-02-14 8:49 ` Gary Bisson
2017-02-14 9:03 ` 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=20170214094436.224c3db8@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