-
Notifications
You must be signed in to change notification settings - Fork 809
[CI] Remove dependency on bot user for uploading benchmark CI results #20333
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
base: sycl
Are you sure you want to change the base?
Conversation
|
||
permissions: | ||
contents: read | ||
contents: write |
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.
can we set the write
permission only at the job step(s) that ened it?
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 attempt this and I'll get back to you
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.
Looks like permissions have a job-level granularity, I can't just give it to a single step.
Doesn't make much sense to nest an additional write permission for the job given that there is only a single job in the entire workflow, are we cool to keep it like this?
env: | ||
RUNNER_TAG: ${{ inputs.runner }} | ||
GITHUB_TOKEN: ${{ secrets.LLVM_SYCL_BENCHMARK_TOKEN }} | ||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} |
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.
can we try removing this line? i think GITHUB_TOKEN
is automatically passed
results_file="$(git diff HEAD~1 --name-only -- results/ | head -n 1)" | ||
if git push "https://[email protected]/intel/llvm-ci-perf-results.git" "$results_branch"; then | ||
if git push; then |
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.
dont we need to specify the 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.
Looks to be already configured by actions/checkout@v5; I figured it was better to specify the branch once than to specify the branch multiple times.
This PR:
benchmark-ci-tests
branch instead of intel/llvm-ci-perf-resultsTest run: https://github.com/intel/llvm/actions/runs/18386952310/job/52388325821 (job failed due to "regression"; issue should be addressed with the merge of #20277