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

flake: always run benchmark-diff effect #178

Merged
merged 2 commits into from
Jan 24, 2022
Merged

Conversation

emiflake
Copy link
Collaborator

@emiflake emiflake commented Jan 24, 2022

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.

srid
srid previously approved these changes Jan 24, 2022
Copy link
Collaborator

@MatthewCroughan MatthewCroughan left a 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.

@emiflake
Copy link
Collaborator Author

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.

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.

@MatthewCroughan
Copy link
Collaborator

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.

@srid
Copy link
Member

srid commented Jan 24, 2022

Simply make a PR targeting staging, and you'll get a benchmark

You will not get a benchmark diff (against staging). See #173 for an example. And that's what this PR fixes.

@emiflake
Copy link
Collaborator Author

Simply make a PR targeting staging, and you'll get a benchmark.

Except, sadly that's not true. See bfd237b. This is on a PR for #173.

image
image

@MatthewCroughan
Copy link
Collaborator

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.

@emiflake
Copy link
Collaborator Author

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 runIf, can we?

@srid srid requested a review from MatthewCroughan January 24, 2022 23:41
flake.nix Show resolved Hide resolved
@srid
Copy link
Member

srid commented Jan 24, 2022

Oh I hadn't noticed that the PR diff changed.

@srid srid requested a review from MatthewCroughan January 24, 2022 23:45
@srid srid merged commit 5860584 into staging Jan 24, 2022
@emiflake emiflake deleted the emiflake/always-benchmark-diff branch March 11, 2022 15:58
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.

3 participants