Investigate segfaults in Squeak Tests

[timfel]

No description provided.

[timfel]

The following tests hang, segfault, or run out of memory:

IntegerDigitLogicTest>>#testLargeShift
TestObjectsAsMethods>>#testDNU
IntegerTest>>#testNegativeIntegerPrinting
SUnitTest>>#testTestTimeoutLoop
NumberParsingTest>>#testFloatmin
TestValueWithinFix>>#testValueWithinNonLocalReturnFixReal
MirrorPrimitiveTests>>#testMirrorInstVarAt
SqueakSSLTest>>#testConnectAccept
FloatTest>>#testHugeIntegerCloseTo
SecureHashAlgorithmTest>>#testEmptyInput
PureBehaviorTest>>#testUpdateWhenLocalMethodRemoved

[timfel]

Now remaining crashes are:

SUnitTest>>#testTestTimeoutLoop # hangs
TestValueWithinFix>>#testValueWithinNonLocalReturnFixReal
SqueakSSLTest>>*
PureBehaviorTest>>#testUpdateWhenLocalMethodRemoved

[timfel]

Down to

• SUnitTest>>#testTestTimeoutLoop -> hangs
• TestValueWithinFix>>#testValueWithinNonLocalReturnFixReal -> crashes trying to fetch a bytecode from a returned method
• SqueakSSLTest>>* different uncaught errors and double free corruptions

[timfel]

@fniephaus: Now that we shouldn't segfault or hang for most tests, do you think we could set up a SmalltalkCI config to run in-image tests, excluding those three that don't work right now?

[timfel]

All SqueakSSLTests are now running as of f2b4b50

[fniephaus]

@timfel do you want to run in-image tests right after building a vm?

[timfel]

no, i was thinking of a setup like RSqueak-App, with a cron job that runs tests daily, maybe split into jobs for groups of core packages

[fniephaus]

Like RSqueak-App or as part of RSqueak-App? Any idea how long all test need to run on a current RSqueak vm?