-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
adjusts timeout, only report 1 issue #156287
adjusts timeout, only report 1 issue #156287
Conversation
@elasticmachine merge upstream |
@@ -7,6 +7,7 @@ | |||
*/ | |||
|
|||
module.exports = { | |||
bail: true, // only report 1 issue |
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.
Yeah, I'm not sure about this.
Yes, when the test suite fails during setup
, it avoid our GH notifications being flooded.
BUT it also means that in case of real failures (e.g when developing on the domain), we can't rely on the CI to list all the failures and we must run the suite(s) manually locally.
So... yeah, idk
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.
yea, I was testing different ways to resolve the failures.
@pgayvallet I've removed bail
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.
report all issues
src/core/server/integration_tests/saved_objects/migrations/group1/jest.integration.config.js
Outdated
Show resolved
Hide resolved
…up1/jest.integration.config.js
💚 Build Succeeded
Metrics [docs]Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
fix #156244
Adjust timeout, only report one issue.