Marc Brockschmidt <[email protected]> writes: [ruby1.9.1 woes] > Sorry for the delay. I've now done a test-build on lebrun, which got > further than our last build-log. I didn't finish the build, though, as > CPU cycles on sparc are currently needed for the build queue. > > I've given back ruby1.9.1 now, let's see if this also works under > sbuild.
It doesn't. I couldn't believe it, so I did yet another manual build,
which now hangs in the test suite:
TestProc#test_splat_without_respond_to: 0.00 s: .
TestProc#test_to_proc: 0.00 s: .
TestProc#test_to_s: 0.00 s: .
TestProcess#test_abort:
The compile problem just went away. The build environments are
identical: Both the failing buildd-triggered process and my manual
rebuild used snapshots of the same lv source. Any ideas?
Marc
--
Fachbegriffe der Informatik - Einfach erklärt
129: Knigge
Kofler des erfolgreichen Kommunizierens (Heinrich Konrad
Bartels)
pgpqm0JdIkjxd.pgp
Description: PGP signature
