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.

Sign up for GitHub

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

Jump to bottom

[CI Problem] Crashed Cases Haven't Catched by CI #16632

Open
Johnson9009 opened this issue Feb 23, 2024 · 2 comments
Open

[CI Problem] Crashed Cases Haven't Catched by CI #16632

Johnson9009 opened this issue Feb 23, 2024 · 2 comments
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

@Johnson9009
Copy link
Contributor

After sync the recent code to our internal environment, and run the tests, we found some items in unittest are crashed, e.g., tests/python/tir-transform, then I found they are crashed in TVM official CI too.

https://ci.tlcpack.ai/blue/rest/organizations/jenkins/pipelines/tvm-cpu/branches/main/runs/1374/nodes/91/steps/207/log/?start=0

image

So it seems like the CI have some problem, it can't catch the crashed cases.
@Johnson9009 Johnson9009 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 Feb 23, 2024
@Johnson9009
Copy link
Contributor Author

@tqchen @junrushao @Hzfengsy

@Johnson9009 Johnson9009 mentioned this issue Feb 23, 2024
Merged
@Johnson9009
Copy link
Contributor Author

This issue used to record and tracking the bug of CI itself, the broken test cases is tracking by #16633.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Johnson9009