Mailinglist Archive: opensuse-buildservice (86 mails)

< Previous Next >
Re: [opensuse-buildservice] Extract artifacts from the failed build
Hi,

Am 21.06.2016 um 10:44 schrieb Matwey V. Kornilov:

Hello,

I suppose that there is a feature currently missed from OBS.
There should be a way to inspect file system for a failed build (ok, I
know that it is probably impossible to implement).

There are kind of build failures hard to deal without possibility to
extract/inspect failed build results from worker.
I agree, that would be a good feature, I missed this from time to time
as well.

1) Occasional build failures due to gcc compiler SIGSEGMs of Golang
SIGILLs which appear on some workers, on other they don't, and the
issues is not reproducible by `osc build local'.

We had this type of errors a while ago. In the end it was buggy
hardware, memtest overnight found errors. Since then we do not longer
use old desktop hardware as workers for production systems.

2) Occasional build failures on non-x86 architectures. It is really hard
to do `osc build local` for linux kernel on armv7l to see why gcc
crashed and produce useful info for gcc bugzilla.

I do understand that it is impossible to save file system for every
failed build and can't propose how could this be implemented.
I imagine some pluggable on-failed hook which packs whole /home/abuild
as single rpm/tgz package and then makes it available through `osc
getbinaries'


A other approach could be to stop the build, let the worker running,
but disable it in the worker pool for some time and inform people. Of
course this should be not the default action, but maybe controlled by
some special flag in the package.

Karsten

--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-buildservice+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References