Skip to content
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

Closed
dalehenrich opened this issue Sep 29, 2014 · 9 comments

Comments

@dalehenrich
Copy link
Member

**************************************************************************************
Results for #('BaselineOfMetacello') Test Suite
510 run, 509 passes, 0 expected failures, 0 failures, 1 errors, 0 unexpected passes
**************************************************************************************
*** ERRORS *******************
MetacelloGithubIssue175TestCase debug: #testIssue175.
**************************************************************************************
@dalehenrich
Copy link
Member Author

and another (Squeak-4.5 only):

**************************************************************************************
    Results for #('BaselineOfMetacello') Test Suite
540 run, 539 passes, 0 expected failures, 0 failures, 1 errors, 0 unexpected passes
**************************************************************************************
*** ERRORS *******************
    MetacelloScriptingDocumentationIssue196TestCase debug: #testLockCommandReference3.
**************************************************************************************

@dalehenrich
Copy link
Member Author

and another (Squeak-4.5 only):

**************************************************************************************
    Results for #('BaselineOfMetacello') Test Suite
540 run, 538 passes, 0 expected failures, 0 failures, 2 errors, 0 unexpected passes
**************************************************************************************
*** ERRORS *******************
    MetacelloScriptingDocumentationIssue196TestCase debug: #testLockCommandReference2.
    MetacelloScriptingDocumentationIssue196TestCase debug: #testLockCommandReference6.
**************************************************************************************

@dalehenrich
Copy link
Member Author

@dalehenrich
Copy link
Member Author

Latest squeak 4 random test failure:

**************************************************************************************
*** ERRORS *******************
MetacelloScriptingIssuesTestCase debug: #testIssue234a.
**************************************************************************************

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...

dalehenrich added a commit that referenced this issue Oct 17, 2014
dalehenrich added a commit that referenced this issue Oct 17, 2014
…itories ... remove MetacelloScriptingGetTestCase logging ... cross fingers
@dalehenrich
Copy link
Member Author

Official list of supsected random test errors (check them off when root cause determined):

  • MetacelloScriptingIssuesTestCase debug: #testIssue234a (Squeak-4.4).
  • MetacelloScriptingSuccessTestCase debug: #testGitHubTagPatternLoad2 (Pharo-3.0)
  • MetacelloScriptingSuccessTestCase debug: #testGitHubTagPatternLoad2B (Pharo-3.0)
  • MetacelloScriptingSuccessTestCase debug: #testGitHubTagPatternLoad3 (Pharo-3.0)

dalehenrich added a commit that referenced this issue Oct 18, 2014
…emingly random failures (not all platforms)
@dalehenrich
Copy link
Member Author

api rate limits for Pharo-3.0 (only one platform so far):

*** ERRORS *******************
MetacelloScriptingSuccessTestCase debug: #testGitHubTagPatternLoad2.
MetacelloScriptingSuccessTestCase debug: #testGitHubTagPatternLoad2B.
MetacelloScriptingSuccessTestCase debug: #testGitHubTagPatternLoad3.
**************************************************************************************
'API rate limit exceeded for 199.91.170.105. (But here''s the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)'

@dalehenrich
Copy link
Member Author

API rate limit exceeded for 199.182.120.5 - GemStone-3.2.2

dalehenrich added a commit that referenced this issue Oct 18, 2014
….... remove MetacelloAtomicLoadOrderTest>>testBaseline10LoadAtomic logging
@dalehenrich
Copy link
Member Author

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

dalehenrich added a commit that referenced this issue Oct 18, 2014
…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
dalehenrich added a commit that referenced this issue Oct 18, 2014
dalehenrich added a commit that referenced this issue Oct 18, 2014
@dalehenrich
Copy link
Member Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant