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

fix(betterer 🐛): force ci to fail when results got worse #596

Merged
merged 1 commit into from
Mar 12, 2021

Conversation

shian15810
Copy link
Contributor

Fixes #595.

@phenomnomnominal
Copy link
Owner

This looks good, not sure why the tests failed so I retriggered it. Could you please add a new test that checks this new behaviour?

@shian15810
Copy link
Contributor Author

Yeah sure! Let me add a new test.

@shian15810
Copy link
Contributor Author

@phenomnomnominal Done, please take a look again. Can you release a new version after this is merged? Thanks!

@shian15810 shian15810 changed the title fix(betterer 🐛): force ci to fail when results get worse fix(betterer 🐛): force ci to fail when results got worse Mar 11, 2021
@shian15810
Copy link
Contributor Author

shian15810 commented Mar 11, 2021

The extension build failed again, not sure why~

@phenomnomnominal
Copy link
Owner

Ugh yeah there's something flaky in that test, it's most likely fine!

@phenomnomnominal phenomnomnominal merged commit f1eb769 into phenomnomnominal:master Mar 12, 2021
@shian15810 shian15810 deleted the patch-1 branch March 12, 2021 09:46
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.

Should CI mode fails if .betterer.results is getting worse?
2 participants