Open fniephaus opened 6 years ago
This one is probably related to a possible VM bug related to image segments. As a side effect, executing ImageSegmentTest will break the image. It would make it easier to track down issues like this if the name of the executed test case appeared in the log.
Good point, I should turn that on, so we see what test cases are causing crashes...
Hi Fabio,
I'd love to take a look at this. But how do I go from { "os": "osx", "script": "./prepare.sh", "language": "smalltalk", "osx_image": "xcode7.3", "smalltalk": "Squeak64-trunk" } to what's actually run on the command line?
@eliotmiranda have a look at squeak-app. prepare.sh
is the entry point and the builds fail here. All files that are needed are in that repository. It's basically calling out to smalltalkCI which then runs all SUnit tests with a few exceptions. Otherwise, download the latest Squeak-trunk
and run all tests a few times. Eventually, you'll get crashes like this.
CI builds still suffer from crashes caused by this, see https://github.com/hpi-swa/smalltalkCI/issues/440 for example. Anyone willing to look into this?
OSVM
201804030952
sometimes crashes inContext(Object)>copy
when running Squeak SUnit tests.Full stack trace at: https://travis-ci.org/squeak-smalltalk/squeak-app/jobs/387262157#L2073
Another trace is at: https://travis-ci.org/squeak-smalltalk/squeak-app/jobs/382950107#L1717