-
Notifications
You must be signed in to change notification settings - Fork 70
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
Manual dispatch perf compare #443
Conversation
Running benchmarks for JikesRVM... |
Running benchmarks for OpenJDK... |
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.
LGTM. Please take a look at that one line of comment I added. I think it's worth clarifying why we need that conditional.
Yeah. That looks fine. Thanks for the review. I will merge this PR later (possibly right before #444 ). |
This PR makes some changes to our perf comparison workflow. The current perf comparison is triggered by commits in a PR with the 'PR-benchmarking' label. After the change, the perf comparison is manually triggered with a
workflow_dispatch
event with a pull request number as its input. We can either run a workflow from the Github API inActions
, or later send the event from our bot when detecting certain comments in a PR.This change achieves two goals:
GITHUB_TOKEN
for the workflows which may not have access to our internal repos).This PR:
pull_request
toworkflow_dispatch
Note that as
workflow_dispatch
cannot be triggered from a branch (only the workflow inmaster
can be triggered), I am not able to test this. I tried to test the change with apull_request
trigger, and it worked fine, and I reverted the trigger (see: ea4980d). However, it is possible that this PR does not work, and requires further fix.