From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 14 Feb 2017 09:44:36 +0100 Subject: [Buildroot] [PATCH] glmark2: bump version In-Reply-To: References: <20170213200619.10535-1-gary.bisson@boundarydevices.com> <20170213223900.7167f053@free-electrons.com> Message-ID: <20170214094436.224c3db8@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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