-
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
[FLAKY] tvmc/test_frontends.py #7455
Comments
Happened again this morning: https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/570/pipeline Relevant traceback:
|
cc @ekalda |
Very odd. It looks like CI is always either skipping that test or failing with that error. That test is passing for me locally though, so I'm not sure how to reproduce it... |
@ekalda are you using the docker container to reproduce? e.g. |
On a quick look in the CI jobs all the posted links so far (including the ones by @apivovarov) it looks like the job was always being executed by Looking at random on recent builds: Any idea on how this could be an infrastructure fail rather than a flaky test? (cc @areusch @masahi ) |
@areusch I built and ran the tests in this docker container using the commands you gave me and I see this test being skipped (similarly to the successful CI runs), which makes me suspect that there is some CI problem... |
FYI this test is getting disabled in #7465 |
This test was originally disabled due to the issue documented in apache#7455 affecting CI. I believe this has since been resolved by apache#9362. Note: This patch should not be merged until the changes in https: //github.com/tlc-pack/tlcpack/pull/81 are reflected in CI. Change-Id: Ib918595a1d9149e3c858ca761861304450cbfe13
This test was originally disabled due to the issue documented in apache#7455 affecting CI. I believe this has since been resolved by apache#9362. Note: This patch should not be merged until the changes in https: //github.com/tlc-pack/tlcpack/pull/81 are reflected in CI. Change-Id: Ib918595a1d9149e3c858ca761861304450cbfe13
This test was originally disabled due to the issue documented in #7455 affecting CI. I believe this has since been resolved by #9362. Note: This patch should not be merged until the changes in https: //github.com/tlc-pack/tlcpack/pull/81 are reflected in CI. Change-Id: Ib918595a1d9149e3c858ca761861304450cbfe13
I believe this can be closed now. |
This test was originally disabled due to the issue documented in apache#7455 affecting CI. I believe this has since been resolved by apache#9362. Note: This patch should not be merged until the changes in https: //github.com/tlc-pack/tlcpack/pull/81 are reflected in CI. Change-Id: Ib918595a1d9149e3c858ca761861304450cbfe13
This test was originally disabled due to the issue documented in apache#7455 affecting CI. I believe this has since been resolved by apache#9362. Note: This patch should not be merged until the changes in https: //github.com/tlc-pack/tlcpack/pull/81 are reflected in CI. Change-Id: Ib918595a1d9149e3c858ca761861304450cbfe13
This test was originally disabled due to the issue documented in apache#7455 affecting CI. I believe this has since been resolved by apache#9362. Note: This patch should not be merged until the changes in https: //github.com/tlc-pack/tlcpack/pull/81 are reflected in CI. Change-Id: Ib918595a1d9149e3c858ca761861304450cbfe13
This test was originally disabled due to the issue documented in apache#7455 affecting CI. I believe this has since been resolved by apache#9362. Note: This patch should not be merged until the changes in https: //github.com/tlc-pack/tlcpack/pull/81 are reflected in CI. Change-Id: Ib918595a1d9149e3c858ca761861304450cbfe13
There is another CI incident on
main
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/activity?branch=mainhttps://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/561/pipeline/
https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/main/560/pipeline/
The error is the same one discussed in #7366. Could be due to the recurring omp + pytorch issue
@jwfromm @comaniac @leandron @altanh
The text was updated successfully, but these errors were encountered: