-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
build: allow db2 tests to fail #13936
Conversation
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.
That's weird. Is there a reason why db2 was allowed to fail?
I guess we did that because it was considered experimental. It seems semi stable however? |
They are two flaky tests for DB2 (especially for Node 12) but in general it seems to be running fine. At least we can see that some tests have failed. Maintainers can still merge even if DB2 tests fail because they are not required so there is no big harm in this change. But I'll leave it up to you @sdepold to merge |
Aaaand it is optional for the release step 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.
I thought it's just worked like p-retry when we scrape something and got cloudflare in front of us but it turns out it's not.
LGTM.
I think I get why the tests were allowed to fail now 😅 |
😅 |
🎉 This PR is included in version 7.0.0-alpha.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I noticed that DB2 tests were failing but CI still let them pass, this should solve that