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 Problem] failed docs push to https://github.com/apache/tvm-site.git #12600

Closed
cconvey opened this issue Aug 25, 2022 · 2 comments · Fixed by #12810
Closed

[CI Problem] failed docs push to https://github.com/apache/tvm-site.git #12600

cconvey opened this issue Aug 25, 2022 · 2 comments · Fixed by #12810
Labels
actionable has an immediately do-able work plan and a detailed description type:ci Relates to TVM CI infrastructure

Comments

@cconvey
Copy link
Contributor

cconvey commented Aug 25, 2022

Branch/PR Failing

5cef6bf
13ebbfb

Jenkins Link

https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/4129/pipeline/
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/4144/pipeline/

Flakiness

Multiple commits (see above)

@cconvey cconvey added the needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it label Aug 25, 2022
@driazati
Copy link
Member

This usually happens since there is a merge race to update the docs between two commits. The best way to fix would be to check the hash in this file and:

  • if it's newer: give up since the docs have already been built and pushed including this commit
  • if it's older: force push the new changes

@driazati driazati added type:ci Relates to TVM CI infrastructure actionable has an immediately do-able work plan and a detailed description and removed needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it labels Aug 25, 2022
@cconvey
Copy link
Contributor Author

cconvey commented Aug 26, 2022

driazati added a commit to driazati/tvm that referenced this issue Sep 6, 2022
Fixes apache#12600. The original solution there doesn't actually fix the
issue, there would need to be some job queue that could make sure to
reject old pushes. Since this case is pretty rare, generally the next
commit that comes along and builds will fix everything up so we can
ignore failures that happen on `push`es.
driazati added a commit to driazati/tvm that referenced this issue Sep 16, 2022
This was missing a repo checkout and failing as in
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/4302/pipeline.
This also adds in the changes from apache#12719:

Fixes apache#12600. The original solution there doesn't actually fix the
issue, there would need to be some job queue that could make sure to
reject old pushes. Since this case is pretty rare, generally the next
commit that comes along and builds will fix everything up so we can
ignore failures that happen on `push`es.
driazati added a commit to driazati/tvm that referenced this issue Sep 16, 2022
This was missing a repo checkout and failing as in
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/4302/pipeline.
This also adds in the changes from apache#12719:

Fixes apache#12600. The original solution there doesn't actually fix the
issue, there would need to be some job queue that could make sure to
reject old pushes. Since this case is pretty rare, generally the next
commit that comes along and builds will fix everything up so we can
ignore failures that happen on `push`es.
driazati added a commit that referenced this issue Sep 16, 2022
This was missing a repo checkout and failing as in
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/4302/pipeline.
This also adds in the changes from #12719:

Fixes #12600. The original solution there doesn't actually fix the
issue, there would need to be some job queue that could make sure to
reject old pushes. Since this case is pretty rare, generally the next
commit that comes along and builds will fix everything up so we can
ignore failures that happen on `push`es.
xinetzone pushed a commit to daobook/tvm that referenced this issue Nov 25, 2022
This was missing a repo checkout and failing as in
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/4302/pipeline.
This also adds in the changes from apache#12719:

Fixes apache#12600. The original solution there doesn't actually fix the
issue, there would need to be some job queue that could make sure to
reject old pushes. Since this case is pretty rare, generally the next
commit that comes along and builds will fix everything up so we can
ignore failures that happen on `push`es.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
actionable has an immediately do-able work plan and a detailed description type:ci Relates to TVM CI infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants