-
Notifications
You must be signed in to change notification settings - Fork 178
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
feat(ci): analyses snapshot skip pr on fail label #15792
Conversation
Proof
|
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.
Cool, thanks!
I have been thinking that this behavior should be the default. Like, we'd somehow get it so that if a snapshot test fails, you get just a normal red X in the CI section. And if you want a PR, you need to take some deliberate action, like commenting with a /slashcommand
, tagging the PR with a magic tag, clicking a magic link, merging from a magic branch, or just doing it locally.
Because a recurring situation seems to be:
- Analysis snapshot tests start failing on
edge
for whatever reason - 5 people branch their PRs off of
edge
- The snapshot tests fail in those 5 people's PRs
- The system creates 5 snapshot PRs
(1)-(3) happen occasionally for normal tests and it's merely mildly annoying; (4) is the thing that's been uniquely noisy about snapshot tests.
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.
oooh... fancy.
I do agree with Max about how noisy the snapshots are.
I like the idea of a /command on the PR
Agree with @DerekMaggio and @SyntaxColoring Also can we get the opened PR (if it does exist) to link to the pr for the branch that it's targeting, if possible? And ideally backlink to itself in the comment on that PR? |
Addressed the comments. Went with label as it is more visible than a comment and easier to handle for this binary circumstance. |
A PR has been opened to address analyses snapshot changes. Please review the changes here: https://github.com/Opentrons/opentrons/pull/ |
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.
Thank you!
{ | ||
"commandType": "home", | ||
"completedAt": "TIMESTAMP", | ||
"createdAt": "TIMESTAMP", | ||
"id": "UUID", | ||
"key": "50c7ae73a4e3f7129874f39dfb514803", | ||
"notes": [], | ||
"params": {}, | ||
"result": {}, | ||
"startedAt": "TIMESTAMP", | ||
"status": "succeeded" | ||
}, |
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.
Reminder to undo this if it was just a change for testing.
commit-message: 'fix(analyses-snapshot-testing): heal analyses snapshots' | ||
title: 'fix(analyses-snapshot-testing): heal ${{ env.ANALYSIS_REF }} snapshots' | ||
body: 'This PR was requested on the PR https://github.com/${{ github.repository }}/pull/${{ github.event.pull_request.number }}' |
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.
Very nice.
A PR has been opened to address analyses snapshot changes. Please review the changes here: https://github.com/Opentrons/opentrons/pull/ fixed this issue where the pr number was not being added to the URL correctly |
A PR has been opened to address analyses snapshot changes. Please review the changes here: #15803 The above was on purpose to see the PR was opened with a link correctly after adding the tag. |
Overview
Keep making the analyses snapshot test workflow more flexible allowing a label on the PR to prevent failure PRs from opening. Adding the labelno-analyses-snapshot-pr
on your PR will cause the workflow to skip opening a PR for snapshot updates if the snapshot tests fail.Updates from feedback
OPEN_PR_ON_FAILURE
to falsegen-analyses-snapshot-pr
label and a PR will get openedRisk
No risk or change to application code, CI only