[opensuse-packaging] Hermes mail about failure [Fwd: Build failure of Base:System/coreutils-testsuite openSUSE_Factory/x86_64]
Hi *, I'm often receiving Hermes mails about build failures (like the following), but I can't see any problem in the log. Any hint? Thanks & have a nice day, Berny -------- Original Message -------- From: hermes@opensuse.org Subject: Build failure of Base:System/coreutils-testsuite openSUSE_Factory/x86_64 X-Hermes-Msg-Type: OBS_BUILD_FAIL X-Mailer: openSUSE Notification System Date: Thu, 26 Sep 2013 04:20:31 +0000 Message-Id: <20130926042031.CB84723C6C@dhl.opensuse.org> Package coreutils-testsuite (version 8.21-216.26) of project Base:System failed to build for openSUSE_Factory / x86_64. Review the build log: osc remotebuildlog Base:System coreutils-testsuite openSUSE_Factory x86_64 | less Check out the package for editing: osc checkout Base:System coreutils-testsuite -- Hermes messaging (http://hermes.opensuse.org) openSUSE Build Service (https://build.opensuse.org/) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 09/26/2013 07:40 AM, Bernhard Voelker wrote:
I'm often receiving Hermes mails about build failures (like the following), but I can't see any problem in the log.
ah, now I see: what I get with 'osc rbl' is always from the latest build, in this case "8.21-216.28" ... osc remotebuildlog Base:System coreutils-testsuite openSUSE_Factory x86_64 | tail -n4 [ 2665s] coreutils-testsuite-8.21-216.28.x86_64.rpm [ 2665s] coreutils-testsuite-8.21-216.28.src.rpm [ 2665s] _statistics [ 2665s] rpmlint.log ... while the failure was in "8.21-216-26":
-------- Original Message -------- From: hermes@opensuse.org Subject: Build failure of Base:System/coreutils-testsuite openSUSE_Factory/x86_64 X-Hermes-Msg-Type: OBS_BUILD_FAIL X-Mailer: openSUSE Notification System Date: Thu, 26 Sep 2013 04:20:31 +0000 Message-Id: <20130926042031.CB84723C6C@dhl.opensuse.org>
Package coreutils-testsuite (version 8.21-216.26) of project Base:System failed to build for openSUSE_Factory / x86_64.
I don't see a command option to view the build log of exactly that build number. Is there a chance to see that? Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 26.09.2013 07:53, Bernhard Voelker wrote:
On 09/26/2013 07:40 AM, Bernhard Voelker wrote:
I'm often receiving Hermes mails about build failures (like the following), but I can't see any problem in the log.
ah, now I see: what I get with 'osc rbl' is always from the latest build, in this case "8.21-216.28" ...
osc remotebuildlog Base:System coreutils-testsuite openSUSE_Factory x86_64 | tail -n4 [ 2665s] coreutils-testsuite-8.21-216.28.x86_64.rpm [ 2665s] coreutils-testsuite-8.21-216.28.src.rpm [ 2665s] _statistics [ 2665s] rpmlint.log
... while the failure was in "8.21-216-26":
-------- Original Message -------- From: hermes@opensuse.org Subject: Build failure of Base:System/coreutils-testsuite openSUSE_Factory/x86_64 X-Hermes-Msg-Type: OBS_BUILD_FAIL X-Mailer: openSUSE Notification System Date: Thu, 26 Sep 2013 04:20:31 +0000 Message-Id: <20130926042031.CB84723C6C@dhl.opensuse.org>
Package coreutils-testsuite (version 8.21-216.26) of project Base:System failed to build for openSUSE_Factory / x86_64.
I don't see a command option to view the build log of exactly that build number. Is there a chance to see that?
No, we don't keep that. But the package fails randomly it seems: osc jobhistory Base:System coreutils-testsuite openSUSE_Factory x86_64 2013-09-18 06:48:24 coreutils-testsuite meta change succeeded 42m 40s build33:2 2013-09-19 16:56:18 coreutils-testsuite meta change succeeded 43m 29s cloud124:1 2013-09-20 06:08:30 coreutils-testsuite meta change failed 8h 12m 20s build13/7 2013-09-25 04:20:36 coreutils-testsuite meta change succeeded 43m 10s cloud118:4 2013-09-25 06:00:41 coreutils-testsuite rebuild counter failed 54m 24s build24:2 2013-09-25 07:07:10 coreutils-testsuite meta change succeeded 1h 6m 12s build11/2 2013-09-25 17:25:44 coreutils-testsuite meta change failed 1h 2m 49s build13/6 2013-09-25 20:59:13 coreutils-testsuite meta change succeeded 44m 40s cloud128:1 2013-09-26 03:14:56 coreutils-testsuite meta change succeeded 44m 44s build31:8 2013-09-26 04:52:35 coreutils-testsuite rebuild counter succeeded 44m 39s cloud124:3 Or Base:System is just randomly broken ;) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On September 26, 2013 at 8:57 AM Stephan Kulow <coolo@suse.de> wrote:
On 26.09.2013 07:53, Bernhard Voelker wrote: > On 09/26/2013 07:40 AM, Bernhard Voelker wrote: > I don't see a command option to view the build log of exactly > that build number. Is there a chance to see that? > No, we don't keep that.
I see, thanks.
But the package fails randomly it seems: osc jobhistory Base:System coreutils-testsuite openSUSE_Factory x86_64 2013-09-18 06:48:24 coreutils-testsuite meta change succeeded 42m 40s build33:2 2013-09-19 16:56:18 coreutils-testsuite meta change succeeded 43m 29s cloud124:1 2013-09-20 06:08:30 coreutils-testsuite meta change failed 8h 12m 20s build13/7 2013-09-25 04:20:36 coreutils-testsuite meta change succeeded 43m 10s cloud118:4 2013-09-25 06:00:41 coreutils-testsuite rebuild counter failed 54m 24s build24:2 2013-09-25 07:07:10 coreutils-testsuite meta change succeeded 1h 6m 12s build11/2 2013-09-25 17:25:44 coreutils-testsuite meta change failed 1h 2m 49s build13/6 2013-09-25 20:59:13 coreutils-testsuite meta change succeeded 44m 40s cloud128:1 2013-09-26 03:14:56 coreutils-testsuite meta change succeeded 44m 44s build31:8 2013-09-26 04:52:35 coreutils-testsuite rebuild counter succeeded 44m 39s cloud124:3 Or Base:System is just randomly broken ;)
It should be quite stable on i586 and x86_64, but it currently fails on ppc: a) sometimes 1 test takes too long and therefore runs into a timeout. b) something in glibc (mktemp) seems to have changed a few weeks ago, therefore a valgrind-based test for sort(1) fails since a few weeks. I didn't have the time to handle them yet. Have a nice day, Berny
Bernhard Voelker <mail@bernhard-voelker.de> writes:
I don't see a command option to view the build log of exactly that build number. Is there a chance to see that?
Old build log are not kept. OBS only keeps the log of the last successful build in addition if the last build has failed. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On 26.09.2013 09:08, Andreas Schwab wrote:
Bernhard Voelker <mail@bernhard-voelker.de> writes:
I don't see a command option to view the build log of exactly that build number. Is there a chance to see that?
Old build log are not kept. OBS only keeps the log of the last successful build in addition if the last build has failed.
... but there is no API to retrieve the last success if it's not the current log. It wouldn't help you anyway as you're looking for the other use case. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (3)
-
Andreas Schwab -
Bernhard Voelker -
Stephan Kulow