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

Scale back LSP tests #944

Merged
merged 10 commits into from
May 18, 2022
Merged

Scale back LSP tests #944

merged 10 commits into from
May 18, 2022

Conversation

petervdonovan
Copy link
Collaborator

This scales back LSP tests because they have been taking a little more computational resources on GitHub Actions than is ideal. Additionally, the "build and run" tests are now redundant.

@petervdonovan petervdonovan force-pushed the scale-back-lsp-tests branch 5 times, most recently from 2336607 to bde16fb Compare February 7, 2022 20:46
@petervdonovan
Copy link
Collaborator Author

petervdonovan commented Feb 7, 2022

OK, this PR has changed the tests so that the random number generator's state is different, and now it is blocked by test failures that cannot be reproduced locally. PyLint 2.12.2 seems to be giving different output for the same input and the same OS on GitHub's end in comparison to my machine. This should be fixed, but I am out of ideas for the moment.

EDIT. Problem "fixed" by waiting for months and then rebasing. Probably this is one of the worst ways to fix a persistent problem in our tests, but it seems to be working...

Since those tests were written, this functionality has been used in the runtime tests. If it breaks, the runtime tests will fail.
This failure cannot be reproduced locally, even with the same PyLint version and the same random seed.
This is a response to failures on remote that could not be reproduced locally. It is unclear what causes it, but if it is nondeterminism in order of test execution, then the previous way of fixing the seed was no good. With this approach, the seed will be different for every test run, but at least the seed will be reported so that failures can be debugged.
@petervdonovan petervdonovan force-pushed the scale-back-lsp-tests branch 2 times, most recently from ec582f3 to a2bd658 Compare May 17, 2022 16:13
@petervdonovan petervdonovan marked this pull request as ready for review May 17, 2022 18:46
Copy link
Member

@lhstrh lhstrh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but did you mean to touch reactor-c as part of this PR?

@petervdonovan
Copy link
Collaborator Author

did you mean to touch reactor-c as part of this PR?

Definitely not -- I missed that while I was rebasing.

@petervdonovan petervdonovan merged commit 3a22f1b into master May 18, 2022
@petervdonovan petervdonovan deleted the scale-back-lsp-tests branch May 18, 2022 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants