Skip to content
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

Closed
cconvey opened this issue Oct 31, 2022 · 4 comments · Fixed by #13239
Closed

[CI] Android CI depends on sunsetted jcenter repo #13240

cconvey opened this issue Oct 31, 2022 · 4 comments · Fixed by #13239
Labels
needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it type:ci Relates to TVM CI infrastructure

Comments

@cconvey
Copy link
Contributor

cconvey commented Oct 31, 2022

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

  • needs-triage
  • vert:android

cc @Mousius @areusch @driazati @gigiblender

@cconvey cconvey added needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it type:ci Relates to TVM CI infrastructure labels Oct 31, 2022
@Lunderberg
Copy link
Contributor

Two more cases for #13238 (CI link) and #13024 (CI link). With four failures across multiple PRs, it doesn't look like it is related to any particular change.

@Lunderberg
Copy link
Contributor

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).

image

@Lunderberg
Copy link
Contributor

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.

@Lunderberg
Copy link
Contributor

If I understand the issue correctly, it should be resolved by @driazati 's #13239. Until it lands, however, I would expect all CI instances to fail.

@Lunderberg Lunderberg changed the title [CI Problem] possibly flaky Android CI tests [CI] Android CI depends on sunsetted jcenter repo Oct 31, 2022
driazati added a commit that referenced this issue Oct 31, 2022
This swaps from jcenter to mavenCentral to resolve networking issues. Fixes #13240
xinetzone pushed a commit to daobook/tvm that referenced this issue Nov 10, 2022
This swaps from jcenter to mavenCentral to resolve networking issues. Fixes apache#13240
xinetzone pushed a commit to daobook/tvm that referenced this issue Nov 25, 2022
This swaps from jcenter to mavenCentral to resolve networking issues. Fixes apache#13240
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it type:ci Relates to TVM CI infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants