On 30 October 2013 23:15, Frank Shearar <frank.shearar at gmail.com> wrote:
> http://build.squeak.org/job/SqueakTrunk/574/console shows a typical
> failure in CI at the moment. The relevant output is:
>
> 2013-10-30T22:17:00.132+01:00: Running tests for Tests...
> !!! Killed command 0 for exceeding allotted time: nice
> /home/jenkins/workspace/SqueakTrunk/target/cog.r2776/coglinux/bin/squeak
> -vm-sound-null -vm-display-null
> "/home/jenkins/workspace/SqueakTrunk/target/PostTestTrunkImage.image"
> ../tests.st.
> /home/jenkins/workspace/SqueakTrunk/benchmarks.st
> spawning command 1 with timeout 600 seconds: nice
> /home/jenkins/workspace/SqueakTrunk/target/cog.r2776/coglinux/bin/squeak
> -vm-sound-null -vm-display-null
> "/home/jenkins/workspace/SqueakTrunk/target/PostTestTrunkImage.image"
> ../benchmarks.st
>
> 2013-10-30T23:01:41.404+01:00: Running tests for ToolBuilder-Kernel...
>
> Note that the "!!!" line happens because the running of the full test
> suite took OVER 40 MINUTES. My crummy little laptop chewed through the
> test suite in 10 minutes.

As an aside, this issue causes massive test failures. You can see 62
failures in that build when we should only have something like 5. Note
http://build.squeak.org/job/SqueakTrunk/574/testReport/SystemChangeNotification.Tests/ChangeHooksTest/testClassCommentedEvent/
which shows a neat symptom of the problem: "RemoteString past end of
file" indicates that your changes file has been altered underneath
your feet. In the CI, this happens because the changes file has been
_deleted_ but the tests are still running.

frank