-
Notifications
You must be signed in to change notification settings - Fork 64
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
flake: always run benchmark-diff effect #178
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.
This compares everything against staging. This means that if I make a PR to Master, it will actually lie and mislead me, and make me think it's comparing the performance of my PR, which it would not be. I do not think this should be merged.
1e8f58d
to
76e7a63
Compare
Fair point, I understand the concern. How's this, then. We'll do it when not on master. And assume all PRs follow the staging workflow and are supersets of staging. |
I don't see the point of doing that. Simply make a PR targeting staging, and you'll get a benchmark. There is no other purpose for this effect. All other data is not relevant. We do not have access to the merge-base via Nix until Hercules-CI 0.9 is released. Once that is released, we can do this for any branch, until then we cannot. |
You will not get a benchmark diff (against staging). See #173 for an example. And that's what this PR fixes. |
Ah, okay. That makes sense. Adding the if statement was a mistake from me. It is the case that it will not run until it is merged, which is not correct. |
Yeah, although your concern is still valid. And this still will sort of be misleading in cases where it runs on branches off of master. Though sadly I don't think we can check if "HEAD came after staging" in a |
Oh I hadn't noticed that the PR diff changed. |
Co-authored-by: MatthewCroughan <[email protected]>
Summary: Run benchmark-diff effect on all commits instead of only those on staging.
Essentially, this change is necessary to make the workflow work as intended by #123 (comment).
Now all future PRs (like this one) will actually run the effects and show them in the checks.