-
Notifications
You must be signed in to change notification settings - Fork 792
[CI][Bench] Cleanup in benchmarks jobs and scripts #20369
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
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.
file delete lgtm, didnt check myself to see if its actually dead
devops/scripts/benchmarks/README.md
Outdated
|
||
To execute the benchmarks in CI, navigate to the `Actions` tab and then go to the `Compute Benchmarks` action. Here, you will find a list of previous runs and a "Run workflow" button. Upon clicking the button, you will be prompted to fill in a form to customize your benchmark run. The only mandatory field is the `PR number`, which is the identifier for the Pull Request against which you want the benchmarks to run. | ||
To execute the benchmarks in CI, navigate to the `Actions` tab and then go to the `Run Benchmarks` workflow. Here, you will find a list of previous runs and a "Run workflow" button. Upon clicking the button, you will be prompted to fill in a form to customize your benchmark run. Important field is the `PR number`, which is the identifier for the Pull Request against which you want the benchmarks to run. Instead, you can specify `Commit hash` from within intel/llvm repository, or leave both | ||
empty to run benchmarks against the latest commit from default branch. |
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.
I think that the latest commit from the branch you pick up as the first drop-down list is taken in this case, but please verify that.
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.
Let me double check this, but IIRC that dropdown list version is: Pretty sure this is the case:
- used if PR/commit hash is not provided
- if PR/commit hash is provided, the dropdown list version only affects the version of benchmark workflow/suite used, the build still relies on PR/commit hash field
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.
Done
File delete LGTM, I totally forgot about the aggregate workflow. Thanks for doing the clean up! |
7baf697
to
2ce7e21
Compare
@intel/llvm-gatekeepers , can you please merge? |
Unexpectedly Passed Tests (1): Reported in #20142. Looks to be flaky, so it should be made UNSUPPORTED. |
As observed in intel#20369, the Regression/barrier_with_work.cpp E2E test may pass sporadically. As such it should be made UNSUPPORTED instead of XFAIL. Signed-off-by: Larsen, Steffen <[email protected]>
As observed in #20369, the Regression/barrier_with_work.cpp E2E test may pass sporadically. As such it should be made UNSUPPORTED instead of XFAIL. Signed-off-by: Larsen, Steffen <[email protected]>
sycl-benchmark-aggregate.yml
seems like a dead codecodespell