FWIW, I just tried to run MCMethodDefinitionTest in an updated image and it popped up 3 requests for my initials and failed 3 tests.

Cheers,
Bob

On 10/31/13 5:20 AM, Frank Shearar wrote:
On 30 October 2013 23:15, Frank Shearar <frank.shearar@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.

So: on Windows 8 I cannot reproduce the problem. Would someone with a
Linux machine please try run the full suite of tests? I strongly
suspect we have a dialog popping up, but only on Linux.
I can reproduce the issue with a Cog on Ubuntu. There's no modal
dialog. If I cmd-., I can see that MCMethodDefinitionTest is running.
It looks like it's looping forever in MCMockPackageInfo >>
#changeRecordsForMethod:do:'s

    [position notNil & file notNil]
        whileTrue:
        [file position: (0 max: position-150).  "Skip back to before
the preamble"
        [file position < (position-1)]  "then pick it up from the front"
            whileTrue: [chunk := file nextChunk].

Thoughts?

frank