-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[CI] Android CI depends on sunsetted jcenter repo #13240
Comments
Checking https://status.gradle.com/, it looks like there were some issues reported earlier today that are now listed as being resolved. However, some of the CI failures occurred after the gradle issue was marked as resolved (October 31, 13:26 UTC). |
It looks like there's a stackoverflow post today, that it is the use of jcenter that is the issue, and not gradle in particular. The JCenter repository was sunset last year, and was permanently turned off today. TVM's dependency on JCenter is here. |
This swaps from jcenter to mavenCentral to resolve networking issues. Fixes #13240
This swaps from jcenter to mavenCentral to resolve networking issues. Fixes apache#13240
This swaps from jcenter to mavenCentral to resolve networking issues. Fixes apache#13240
Branch/PR Failing
#13177
Also failing, possibly related: #13130
Jenkins Link
https://github.com/apache/tvm/actions/runs/3356692875/jobs/5563585344
Flakiness
Multiple times in PR 13177 over this past weekend. PR 13130 is also failing Android CI.
Triage
cc @Mousius @areusch @driazati @gigiblender
The text was updated successfully, but these errors were encountered: