Increase Jest timeout for profiling plugin test#8581
Merged
sokra merged 1 commit intowebpack:masterfrom Jan 4, 2019
DanielRuf:tests/increase-jest-timeout
Merged
Increase Jest timeout for profiling plugin test#8581sokra merged 1 commit intowebpack:masterfrom DanielRuf:tests/increase-jest-timeout
sokra merged 1 commit intowebpack:masterfrom
DanielRuf:tests/increase-jest-timeout
Conversation
Contributor
|
For maintainers only:
|
Contributor
|
Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon. |
sokra
approved these changes
Jan 3, 2019
Member
|
Thanks |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR tries to resolve the timeouts in the testsuite (see current CI status).
See https://travis-ci.org/webpack/webpack/jobs/474274728#L536-L538
What kind of change does this PR introduce?
Tests / CI
Did you add tests for your changes?
No
Does this PR introduce a breaking change?
No
What needs to be documented once your changes are merged?