Possible to access Koji build directory?

Jan Kratochvil jan.kratochvil at redhat.com
Fri Mar 16 10:32:54 UTC 2012

On Fri, 16 Mar 2012 11:16:51 +0100, Jim Meyering wrote:
> That works very well.  However, the base64 output in my first log was
> corrupt, due to some asynchronous output (stderr about job completion)
> that was emitted in the middle of the big base64 block.
> Adding the "sync; sleep 10" part below should avoid that in the future:

FYI using automatic killer of leftover processes as some of them never finished
and blocked builds, in other cases they kept running busy on build boxes etc.

# Cleanup any leftover testsuite processes as it may stuck mock(1) builds.
# http://pkgs.fedoraproject.org/gitweb/?p=gdb.git;a=blob_plain;f=gdb-orphanripper.c;hb=master
Source2: gdb-orphanripper.c
gcc -o ./orphanripper %{SOURCE2} -Wall -lutil -ggdb2
./orphanripper make %{?_smp_mflags} -k $CHECK || :


More information about the devel mailing list