* [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-26
@ 2018-03-27 6:00 Thomas Petazzoni
2018-03-27 6:45 ` Baruch Siach
0 siblings, 1 reply; 6+ messages in thread
From: Thomas Petazzoni @ 2018-03-27 6:00 UTC (permalink / raw)
To: buildroot
Hello,
Build statistics for 2018-03-26
===============================
branch | OK | NOK | TIM | TOT |
2018.02.x | 194 | 10 | 0 | 204 |
Results for branch '2018.02.x'
==============================
Classification of failures by reason
------------------------------------
bluez5_utils-5.48 | 2
php-7.2.3 | 2
cc-tool-0.26 | 1
cups-filters-1.17.9 | 1
jamvm-2.0.0 | 1
mplayer-1.3.0 | 1
uclibc-ng-test-c6d62cbc6050... | 1
wireshark-2.2.12 | 1
Detail of failures
------------------
powerpc | bluez5_utils-5.48 | NOK | http://autobuild.buildroot.net/results/1f73577da7e801074280b5fc444edd8536f538f5 |
or1k | bluez5_utils-5.48 | NOK | http://autobuild.buildroot.net/results/bc6711eb27c156060196be65ef9e8ad75ce8ab04 |
m68k | cc-tool-0.26 | NOK | http://autobuild.buildroot.net/results/eefb4fafd4e3a3bec7aad02f2777b68f91f38347 |
arm | cups-filters-1.17.9 | NOK | http://autobuild.buildroot.net/results/1c296fa2a28617746fd72a2d54b8fa9e4278a934 |
mipsel | jamvm-2.0.0 | NOK | http://autobuild.buildroot.net/results/d1cc83a82d85469f3d141f07469d3be3d018d9b6 | ORPH
i586 | mplayer-1.3.0 | NOK | http://autobuild.buildroot.net/results/e411efdcb04a4be54f97a509093d6955e875ed80 |
arm | php-7.2.3 | NOK | http://autobuild.buildroot.net/results/447311bb9ed2bc1040420672ff7157994ce8cdaf | ORPH
arm | php-7.2.3 | NOK | http://autobuild.buildroot.net/results/a6138b36154fc18d956d724ff892e3ac0640208a | ORPH
i586 | uclibc-ng-test-c6d62cbc6050... | NOK | http://autobuild.buildroot.net/results/dfa59e9a658c19598c5ba2264eb66b5e9d0daaba |
powerpc | wireshark-2.2.12 | NOK | http://autobuild.buildroot.net/results/912a867fed30497ed0a6bc563cc6e41e79eca7e0 | ORPH
--
http://autobuild.buildroot.net
^ permalink raw reply [flat|nested] 6+ messages in thread* [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-26 2018-03-27 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-26 Thomas Petazzoni @ 2018-03-27 6:45 ` Baruch Siach 2018-03-27 7:15 ` Thomas Petazzoni 0 siblings, 1 reply; 6+ messages in thread From: Baruch Siach @ 2018-03-27 6:45 UTC (permalink / raw) To: buildroot Hi Thomas, On Tue, Mar 27, 2018 at 08:00:26AM +0200, Thomas Petazzoni wrote: > Build statistics for 2018-03-26 > =============================== > > branch | OK | NOK | TIM | TOT | > 2018.02.x | 194 | 10 | 0 | 204 | No reports on master. The web interface is also not showing recent master builds. The last master build report is from 2018-03-25 22:43:51 (http://autobuild.buildroot.net/results/990/990732326160144b71f30938beb3f208cb882ea4/). baruch -- http://baruch.siach.name/blog/ ~. .~ Tk Open Systems =}------------------------------------------------ooO--U--Ooo------------{= - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il - ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-26 2018-03-27 6:45 ` Baruch Siach @ 2018-03-27 7:15 ` Thomas Petazzoni 2018-03-27 7:44 ` Peter Korsgaard 0 siblings, 1 reply; 6+ messages in thread From: Thomas Petazzoni @ 2018-03-27 7:15 UTC (permalink / raw) To: buildroot Hello, On Tue, 27 Mar 2018 09:45:10 +0300, Baruch Siach wrote: > Hi Thomas, > > On Tue, Mar 27, 2018 at 08:00:26AM +0200, Thomas Petazzoni wrote: > > Build statistics for 2018-03-26 > > =============================== > > > > branch | OK | NOK | TIM | TOT | > > 2018.02.x | 194 | 10 | 0 | 204 | > > No reports on master. The web interface is also not showing recent master > builds. The last master build report is from 2018-03-25 22:43:51 > (http://autobuild.buildroot.net/results/990/990732326160144b71f30938beb3f208cb882ea4/). Well spotted. This is due to commit ea9669fffae7d807ccb3810eb6c662cbb9e8f96f, which removed the core-dependencies target. This target is explicit used by autobuild-run to check if the system has all necessary dependencies, and if not, simply move on to the next build. Due to this, all master configurations fail on "core-dependencies does not exist". The correct target to use now is "dependencies". However, in 2018.02.x, it's still "core-dependencies" that should be used. Using "dependencies" in 2018.02.x would not be good, because "dependencies" triggers the build of host-{tar,xz,ccache,lzip}, and therefore a failure in the build of those packages would not be reported on autobuild.b.o. So I see two options: (1) Re-introduce a "core-dependencies" target, that is the same as the "dependencies" target (2) Tweak the autobuild-run script, and make a special case depending on the branch name: if we're on 2018.02.x, use "core-dependencies", otherwise use "dependencies". Arnout, Peter, any preference ? I'm leaning towards (2) since that's the solution that doesn't pollute Buildroot with unnecessary stuff. Best regards, Thomas -- Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-26 2018-03-27 7:15 ` Thomas Petazzoni @ 2018-03-27 7:44 ` Peter Korsgaard 2018-03-27 7:47 ` Thomas Petazzoni 0 siblings, 1 reply; 6+ messages in thread From: Peter Korsgaard @ 2018-03-27 7:44 UTC (permalink / raw) To: buildroot >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes: Hi, > So I see two options: > (1) Re-introduce a "core-dependencies" target, that is the same as the > "dependencies" target > (2) Tweak the autobuild-run script, and make a special case depending > on the branch name: if we're on 2018.02.x, use "core-dependencies", > otherwise use "dependencies". > Arnout, Peter, any preference ? I'm leaning towards (2) since that's > the solution that doesn't pollute Buildroot with unnecessary stuff. I agree. It does mean that we need all autobuilders to update, but that shouldn't be a big problem. -- Bye, Peter Korsgaard ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-26 2018-03-27 7:44 ` Peter Korsgaard @ 2018-03-27 7:47 ` Thomas Petazzoni 2018-03-27 8:00 ` Peter Korsgaard 0 siblings, 1 reply; 6+ messages in thread From: Thomas Petazzoni @ 2018-03-27 7:47 UTC (permalink / raw) To: buildroot Hello, On Tue, 27 Mar 2018 09:44:36 +0200, Peter Korsgaard wrote: > > Arnout, Peter, any preference ? I'm leaning towards (2) since that's > > the solution that doesn't pollute Buildroot with unnecessary stuff. > > I agree. It does mean that we need all autobuilders to update, but that > shouldn't be a big problem. It also means that if someone uses autobuild-run to test another branch than 2018.02.x, master or next, we have no idea whether we should use "dependencies" or "core-dependencies". But well, I believe autobuild-run is kind of an internal tool, it's not really meant to be used as a generic tool. If people do this, then it's up to them to figure out how to tweak it. Thomas -- Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com ^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-26 2018-03-27 7:47 ` Thomas Petazzoni @ 2018-03-27 8:00 ` Peter Korsgaard 0 siblings, 0 replies; 6+ messages in thread From: Peter Korsgaard @ 2018-03-27 8:00 UTC (permalink / raw) To: buildroot >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes: > Hello, > On Tue, 27 Mar 2018 09:44:36 +0200, Peter Korsgaard wrote: >> > Arnout, Peter, any preference ? I'm leaning towards (2) since that's >> > the solution that doesn't pollute Buildroot with unnecessary stuff. >> >> I agree. It does mean that we need all autobuilders to update, but that >> shouldn't be a big problem. > It also means that if someone uses autobuild-run to test another branch > than 2018.02.x, master or next, we have no idea whether we should use > "dependencies" or "core-dependencies". Unless we detect what make target to use by looking in support/dependencies/dependencies.mk for the 'core-dependencies:' line instead of based on the branch name. > But well, I believe autobuild-run is kind of an internal tool, it's not > really meant to be used as a generic tool. If people do this, then it's > up to them to figure out how to tweak it. I agree. -- Bye, Peter Korsgaard ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2018-03-27 8:00 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2018-03-27 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-26 Thomas Petazzoni 2018-03-27 6:45 ` Baruch Siach 2018-03-27 7:15 ` Thomas Petazzoni 2018-03-27 7:44 ` Peter Korsgaard 2018-03-27 7:47 ` Thomas Petazzoni 2018-03-27 8:00 ` Peter Korsgaard
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox