-
-
Notifications
You must be signed in to change notification settings - Fork 6.6k
Test retries #6498
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
Merged
Merged
Test retries #6498
Changes from 1 commit
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
e99dd90
Enable configurable retries for failed test cases
palmerj3 b265a8b
Update tests
palmerj3 ee92c95
Remove testRetries CLI and config option. Add as jest.retryTimes with…
palmerj3 7d6f27b
Add jest.retryTimes to CHANGELOG.md and JestObjectAPI.md
palmerj3 38ba329
Prettier fix on snapshot test
palmerj3 262e34d
Update runJest to support jest-circus environment override
palmerj3 e9762af
Update docs and use skipSuiteOnJasmine
palmerj3 d1edc37
Update retryTimes tests
palmerj3 09fb974
Remove useJestCircus boolean on runTest
palmerj3 b346cc2
Remove outdated comment. Revert runJest environment override logic.
palmerj3 b9d65f8
Removed outdated comment from test_retries test
palmerj3 20667aa
Update snapshot tests
palmerj3 19bf8a6
Update Jest Object docs for retryTimes. Use symbol for global lookup.
palmerj3 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Update retryTimes tests
- Loading branch information
commit d1edc3712a2208ce207660612498e37325195d9d
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
outdated comment, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep. Pushing a commit now to fix.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmm :P
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All set - still getting CI errors due to the graceful-fs dependency bump yesterday (I believe)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment is still there :D
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI failures are not because of
graceful-fsbump (there wasn't any afaik), but started to happen since Node 10.5