[opensuse-buildservice] Build failures due to OBS
Hi all, Lately I happen to see (felt) more package failures as a result of OBS itself than this used to be. It's kind of 'frustrating' to to local builds that work, check in to OBS and see build failures, then having to figure out that 'oh: once more it was just something that got stuck... let's trigger a rebuild, maybe it helps' Among the errors I keep on seeing are: - decompression errors of RPMs (cpio archive errors) - 'job got stuck'; seen that in the middle of builds or, even more common, at the very end of the build. Example: https://build.opensuse.org/package/live_build_log?arch=i586&package=gnome-keyring&project=GNOME%3AFactory&repository=openSUSE_Factory (I'll try not to trigger a rebuild of that for the next few hours...) Is there any special thing broken (did not verify if I'm always hit by the same worker for example) and are we aware of the breakage? Or is this completely under the radar and needs more empiric findings to make an assumption, what could be at fault? Thanks for your hard work on OBS though! Building packages without it would be worse than the random failures it causes :P Still a positive net value. Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Donnerstag, 1. Dezember 2011, 14:41:14 schrieb Dimstar / Dominique Leuenberger:
Hi all,
Lately I happen to see (felt) more package failures as a result of OBS itself than this used to be.
It's kind of 'frustrating' to to local builds that work, check in to OBS and see build failures, then having to figure out that 'oh: once more it was just something that got stuck... let's trigger a rebuild, maybe it helps'
Among the errors I keep on seeing are: - decompression errors of RPMs (cpio archive errors) - 'job got stuck'; seen that in the middle of builds or, even more common, at the very end of the build. Example: https://build.opensuse.org/package/live_build_log?arch=i586&package=gnome-ke yring&project=GNOME%3AFactory&repository=openSUSE_Factory
(I'll try not to trigger a rebuild of that for the next few hours...)
Is there any special thing broken (did not verify if I'm always hit by the same worker for example) and are we aware of the breakage? Or is this completely under the radar and needs more empiric findings to make an assumption, what could be at fault?
We can't detect such failures automatically ... in this case it was build26. It may be that this host has a problem. Can you check your other failures and check if they were caused by the same host(s) ? It is mentioned at the start of the logfile. The other option is that we may have a broken Factory distro. Are that only Factory builds which fail that way ? -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, 2011-12-01 at 14:52 +0100, Adrian Schröter wrote:
We can't detect such failures automatically ... in this case it was build26. It may be that this host has a problem.
Can you check your other failures and check if they were caused by the same host(s) ?
It is mentioned at the start of the logfile.
The other option is that we may have a broken Factory distro. Are that only Factory builds which fail that way ?
Adrian, I will try to keep an eye on this and hopefully we get an overview of which host is nagging. I think if 'factory' would be broken, then a simple retrigger of the build should not resolve the issue. And I'm honestly not sure if non-factory builds show the same :( I almost exclusively target Factory. Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Donnerstag, 1. Dezember 2011, 14:54:45 schrieb Dimstar / Dominique Leuenberger:
On Thu, 2011-12-01 at 14:52 +0100, Adrian Schröter wrote:
We can't detect such failures automatically ... in this case it was build26. It may be that this host has a problem.
Can you check your other failures and check if they were caused by the same host(s) ?
It is mentioned at the start of the logfile.
The other option is that we may have a broken Factory distro. Are that only Factory builds which fail that way ?
Adrian,
I will try to keep an eye on this and hopefully we get an overview of which host is nagging.
I think if 'factory' would be broken, then a simple retrigger of the build should not resolve the issue.
That depends on the bug, random failures can also be caused by a broken tool chain for example. However, my first check would also be the build host names.
And I'm honestly not sure if non-factory builds show the same :( I almost exclusively target Factory.
Dominique -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, 01 Dec 2011 14:52:02 +0100 Adrian Schröter wrote:
We can't detect such failures automatically ... in this case it was build26. It may be that this host has a problem.
Can you check your other failures and check if they were caused by the same host(s) ?
It is mentioned at the start of the logfile.
The other option is that we may have a broken Factory distro. Are that only Factory builds which fail that way ?
build25 for openSUSE 11.4 https://build.opensuse.org/package/live_build_log?arch=i586&package=kiso&project=KDE%3AKDE3&repository=openSUSE_11.4 -- WBR Kyrill -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Donnerstag, 1. Dezember 2011, 18:10:02 schrieb Kyrill Detinov:
On Thu, 01 Dec 2011 14:52:02 +0100 Adrian Schröter wrote:
We can't detect such failures automatically ... in this case it was build26. It may be that this host has a problem.
Can you check your other failures and check if they were caused by the same host(s) ?
It is mentioned at the start of the logfile.
The other option is that we may have a broken Factory distro. Are that only Factory builds which fail that way ?
build25 for openSUSE 11.4 https://build.opensuse.org/package/live_build_log?arch=i586&package=kiso&pro ject=KDE%3AKDE3&repository=openSUSE_11.4
there is a hanging cpu prompt inside ... so either kernel/kvm or hardware problem .... -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, 2011-12-01 at 15:13 +0100, Adrian Schröter wrote:
build25 for openSUSE 11.4 https://build.opensuse.org/package/live_build_log?arch=i586&package=kiso&pro ject=KDE%3AKDE3&repository=openSUSE_11.4
there is a hanging cpu prompt inside ... so either kernel/kvm or hardware problem ....
Build 32 on openSUSE:Factory https://build.opensuse.org/package/rawlog?arch=i586&package=pdfmod&project=GNOME%3AApps&repository=openSUSE_Factory -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
Adrian Schröter -
Dimstar / Dominique Leuenberger -
Kyrill Detinov