From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glmark2: bump version
Date: Tue, 14 Feb 2017 10:03:04 +0100 [thread overview]
Message-ID: <20170214100304.4970a39f@free-electrons.com> (raw)
In-Reply-To: <CAAMH-yvBA9gpFLNy1Tu+x4A2fFOetdGHgVeLkpnAweBqsUS8iQ@mail.gmail.com>
Hello,
On Tue, 14 Feb 2017 09:49:09 +0100, Gary Bisson wrote:
> No that is what I meant, "injecting" a defconfig so that a problem
> that we see locally can be reproduced by a server and that we know
> there will be a trace of that issue somewhere (with all the proper
> information).
>
> I understand it would be a mess to maintain such infrastructure, but
> at least that would be a go-to response when someone says something is
> broken: put your defconfig on the server and we'll see.
Well, in practice this is not really useful. If a given problem has
been produced by the autobuilders, it's really easy to find it. For
example, for your glmark2 issue, I simply did:
http://autobuild.buildroot.net/?reason=glmark2-fa71af2dfab711fac87b9504b6fc9862f44bf72a
And looked at the last few errors, and they were the ones your patch
was fixing.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-02-14 9:03 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
2017-02-14 8:49 ` Gary Bisson
2017-02-14 9:03 ` Thomas Petazzoni [this message]
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=20170214100304.4970a39f@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