-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
random failures for MetacelloGithubIssue175TestCase>>testIssue175 Squeak4.5 and Squeak Trunk #286
Comments
and another (Squeak-4.5 only):
|
and another (Squeak-4.5 only):
|
Latest squeak 4 random test failure:
After the recent spate of test cleanup work ... the earlier test reports can be ignored unless they repeat again ... will add logging for this boyo... |
…4a ... lastest Squeak-4.4 test error
…itories ... remove MetacelloScriptingGetTestCase logging ... cross fingers
Official list of supsected random test errors (check them off when root cause determined):
|
…emingly random failures (not all platforms)
api rate limits for Pharo-3.0 (only one platform so far):
|
API rate limit exceeded for 199.182.120.5 - GemStone-3.2.2 |
….... remove MetacelloAtomicLoadOrderTest>>testBaseline10LoadAtomic logging
Let's avoid rate limit-related test failures .. if the test hits a rate limit don't fail ... interesting to know, but not worth failing the test over |
…ve repos in tests ... the description of repos can morph during a test and that foils the MCRepositoryGroup>>removeRepository: logic which uses description as part of equality test ... revert MetacelloPlatform>>createRepository: to old behavior of not setting description of a dictionary repo on creation ... still in question though
clean sheet ... dictionary repositories and random package-cache are very likely the culprits for all of the random test failures I've ben seeing lately ... with the recent move to wipe package-cache clean between tests and the use of MCRepositoryGroup>>removeIdenticalRepository: to clean up repos, I'm going to call this issue closed and wait for the next rash of random failures to start popping up |
The text was updated successfully, but these errors were encountered: