Skip to content

Conversation

jsji
Copy link
Contributor

@jsji jsji commented Apr 12, 2024

The update-check started to fail 2 months ago in https://github.com/intel/llvm/actions/runs/8461500755.

Last CUDA e2e success was https://github.com/intel/llvm/actions/runs/8460746056 2 months ago!!
So looks like a problem caused by #13173 again..

@jsji jsji requested a review from a team as a code owner April 12, 2024 13:34
@jsji jsji self-assigned this Apr 12, 2024
@jsji jsji changed the title [CI] Fix status (update_check) permission for sycl cuda e2e [CI] Fix status (update-check) permission for sycl cuda e2e Apr 12, 2024
@jsji
Copy link
Contributor Author

jsji commented Apr 12, 2024

It is still failing. https://github.com/intel/llvm/actions/runs/8664940056/job/23762496288

According to https://docs.github.com/en/rest/commits/statuses?apiVersion=2022-11-28#create-a-commit-status
We may need to double check whether the token we used has the correct "scope". @stdale-intel @intel/dpcpp-devops-reviewers

@jsji jsji marked this pull request as draft April 12, 2024 17:02
@jsji
Copy link
Contributor Author

jsji commented Apr 17, 2024

close this. @stdale-intel has been working with IPAS team to resolve this.

@jsji jsji closed this Apr 17, 2024
@jsji jsji deleted the cudae2epermission branch April 23, 2024 20:38
@jsji jsji restored the cudae2epermission branch May 7, 2024 16:22
@jsji jsji reopened this May 7, 2024
@jsji jsji force-pushed the cudae2epermission branch from 3e64e49 to b256f0a Compare May 7, 2024 16:24
@jsji jsji marked this pull request as ready for review May 7, 2024 16:24
@jsji jsji requested a review from npmiller May 7, 2024 16:26
@aelovikov-intel
Copy link
Contributor

@jsji can you update description please? "two weeks" isn't accurate anymore.

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