On Wed, 2008-02-13 at 07:38 +0000, Kevin Kofler wrote: > Ralf Corsepius <rc040203 <at> freenet.de> writes: > > You call looking at build.logs for several hours and watching them not > > receiving any updates/progress for several hours a premature conclusion? > > > > Sorry, but then koji has a usability problem ... > > How is that Koji's fault? The operating system and/or C library caches stdio > writes, they aren't output immediately unless fflush is explicitly called, and > Koji has no control on the processes which are outputting to the redirected > stdout (make and its subprocesses). stdout/stderr are being flushed upon all "\n"'s. The compiler-call the build job hung on ppc64, on all other architectures takes in the "order of minutes" => the logs are being flushed at the same rate > There's no way to fix that in Koji. no comment. -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
