-
Notifications
You must be signed in to change notification settings - Fork 379
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
CI should detect problems in PRs, not after merging #2531
Labels
Comments
The case I saw today was caused by a PR in examples/, changing the behaviour of a test in gno.land/ (a txtar test). I'm starting to think we should just test everything all the time, also on PRs. |
7 tasks
moul
added a commit
that referenced
this issue
Jul 14, 2024
thehowl
pushed a commit
that referenced
this issue
Jul 14, 2024
gfanton
pushed a commit
to gfanton/gno
that referenced
this issue
Jul 23, 2024
thehowl
added a commit
that referenced
this issue
Jul 24, 2024
There's been another CI fail on master just now, because changes in examples/ were changing the golden output in gnovm/, but gnovm/ was not tested. This PR implements the suggestion I made in #2531 - ie. not discriminating CIs based on the paths of the modified file.
Done with #2625 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We had at least 3 merged pull requests in the last few days (two of them were mine, sorry), and they were green while still unmerged, but they caused the master branch to become red.
We need to fine-tune the CI to prevent this from happening.
The text was updated successfully, but these errors were encountered: