Mailinglist Archive: opensuse-buildservice (86 mails)

< Previous Next >
[opensuse-buildservice] Extract artifacts from the failed build
  • From: "Matwey V. Kornilov" <matwey.kornilov@xxxxxxxxx>
  • Date: Tue, 21 Jun 2016 11:44:07 +0300
  • Message-id: <nkauon$dkl$1@ger.gmane.org>

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.
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'.
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'

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

< Previous Next >
Follow Ups