hpi-swa / RSqueak

A Squeak/Smalltalk VM written in RPython.
BSD 3-Clause "New" or "Revised" License
83 stars 15 forks source link

Investigate segfaults in Squeak Tests #131

Open timfel opened 8 years ago

timfel commented 7 years ago

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 commented 7 years ago

Now remaining crashes are:

SUnitTest>>#testTestTimeoutLoop # hangs
TestValueWithinFix>>#testValueWithinNonLocalReturnFixReal
SqueakSSLTest>>*
PureBehaviorTest>>#testUpdateWhenLocalMethodRemoved
timfel commented 7 years ago

Down to

timfel commented 7 years ago

@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 commented 7 years ago

All SqueakSSLTests are now running as of f2b4b5082b8357c513ef64b8e9e64c7d71b59069

fniephaus commented 7 years ago

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

timfel commented 7 years ago

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 commented 7 years ago

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