-
Notifications
You must be signed in to change notification settings - Fork 795
[CI][Benchmarks] Fix pushing results to new branch #20544
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
18d144a to
1ebf2b4
Compare
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
1ebf2b4 to
8d3aea8
Compare
|
@intel/dpcpp-devops-reviewers, please review. Here is the proper test run for these changes: https://github.com/intel/llvm/actions/runs/19062984825 |
|
@lukaszstolarczuk Done, can I merge or is the Benchmark CI failure related to this PR? |
This doesn't make sense to me. Why are we still pushing to branch in intel/llvm-ci-perf-results? instead of pushing to sycl-benchmark-ci-results branch of intel/llvm |
This patch properly pushes to the branch you mentioned, sycl-benchmark-ci-results. I mistakenly used the wrong name in the PR's description, sorry for confusion. |
|
@intel/llvm-gatekeepers, ready to merge. The CI failure is related to issue mitigated in #20537. The custom run of benchmarks that validates this CI change is here: https://github.com/intel/llvm/actions/runs/19062984825. |
There is a bug that results in Nightly Benchmarks to fail pushing new results to the new results branch on
intel/llvm:This patch fixes the benchmarking workflow to properly push to the correct sycl-benchmark-ci-results branch.