-
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] Segfaults cause pytest internal errors #12776
Labels
Comments
driazati
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
and removed
needs-triage
PRs or issues that need to be investigated by maintainers to find the right assignees to address it
labels
Sep 14, 2022
driazati
added a commit
to driazati/tvm
that referenced
this issue
Sep 20, 2022
This is a less-than-ideal fix for apache#12776. It disables reruns for crashes in xdist workers, which gets rid of the pytest internal failure and correctly reports the test name. Ideally it would also include the backtrace in the report and rerun the test but there doesn't seem to be an easy way to get pytest-rerunfailures to do that alongside the LoadScopeScheduler.
driazati
added a commit
to driazati/tvm
that referenced
this issue
Sep 20, 2022
This is a less-than-ideal fix for apache#12776. It disables reruns for crashes in xdist workers, which gets rid of the pytest internal failure and correctly reports the test name. Ideally it would also include the backtrace in the report and rerun the test but there doesn't seem to be an easy way to get pytest-rerunfailures to do that alongside the LoadScopeScheduler.
driazati
added a commit
to driazati/tvm
that referenced
this issue
Sep 20, 2022
This is a less-than-ideal fix for apache#12776. It disables reruns for crashes in xdist workers, which gets rid of the pytest internal failure and correctly reports the test name. Ideally it would also include the backtrace in the report and rerun the test but there doesn't seem to be an easy way to get pytest-rerunfailures to do that alongside the LoadScopeScheduler.
driazati
added a commit
to driazati/tvm
that referenced
this issue
Sep 20, 2022
This is a less-than-ideal fix for apache#12776. It disables reruns for crashes in xdist workers, which gets rid of the pytest internal failure and correctly reports the test name. Ideally it would also include the backtrace in the report and rerun the test but there doesn't seem to be an easy way to get pytest-rerunfailures to do that alongside the LoadScopeScheduler.
driazati
added a commit
to driazati/tvm
that referenced
this issue
Sep 20, 2022
This is a less-than-ideal fix for apache#12776. It disables reruns for crashes in xdist workers, which gets rid of the pytest internal failure and correctly reports the test name. Ideally it would also include the backtrace in the report and rerun the test but there doesn't seem to be an easy way to get pytest-rerunfailures to do that alongside the LoadScopeScheduler.
driazati
added a commit
to driazati/tvm
that referenced
this issue
Sep 20, 2022
This is a less-than-ideal fix for apache#12776. It disables reruns for crashes in xdist workers, which gets rid of the pytest internal failure and correctly reports the test name. Ideally it would also include the backtrace in the report and rerun the test but there doesn't seem to be an easy way to get pytest-rerunfailures to do that alongside the LoadScopeScheduler.
driazati
added a commit
to driazati/tvm
that referenced
this issue
Sep 26, 2022
This is a less-than-ideal fix for apache#12776. It disables reruns for crashes in xdist workers, which gets rid of the pytest internal failure and correctly reports the test name. Ideally it would also include the backtrace in the report and rerun the test but there doesn't seem to be an easy way to get pytest-rerunfailures to do that alongside the LoadScopeScheduler.
driazati
added a commit
to driazati/tvm
that referenced
this issue
Sep 27, 2022
This is a less-than-ideal fix for apache#12776. It disables reruns for crashes in xdist workers, which gets rid of the pytest internal failure and correctly reports the test name. Ideally it would also include the backtrace in the report and rerun the test but there doesn't seem to be an easy way to get pytest-rerunfailures to do that alongside the LoadScopeScheduler.
driazati
added a commit
to driazati/tvm
that referenced
this issue
Sep 27, 2022
This is a less-than-ideal fix for apache#12776. It disables reruns for crashes in xdist workers, which gets rid of the pytest internal failure and correctly reports the test name. Ideally it would also include the backtrace in the report and rerun the test but there doesn't seem to be an easy way to get pytest-rerunfailures to do that alongside the LoadScopeScheduler.
driazati
added a commit
to driazati/tvm
that referenced
this issue
Sep 28, 2022
This is a less-than-ideal fix for apache#12776. It disables reruns for crashes in xdist workers, which gets rid of the pytest internal failure and correctly reports the test name. Ideally it would also include the backtrace in the report and rerun the test but there doesn't seem to be an easy way to get pytest-rerunfailures to do that alongside the LoadScopeScheduler.
driazati
added a commit
to driazati/tvm
that referenced
this issue
Sep 28, 2022
This is a less-than-ideal fix for apache#12776. It disables reruns for crashes in xdist workers, which gets rid of the pytest internal failure and correctly reports the test name. Ideally it would also include the backtrace in the report and rerun the test but there doesn't seem to be an easy way to get pytest-rerunfailures to do that alongside the LoadScopeScheduler.
driazati
added a commit
to driazati/tvm
that referenced
this issue
Sep 28, 2022
This is a less-than-ideal fix for apache#12776. It disables reruns for crashes in xdist workers, which gets rid of the pytest internal failure and correctly reports the test name. Ideally it would also include the backtrace in the report and rerun the test but there doesn't seem to be an easy way to get pytest-rerunfailures to do that alongside the LoadScopeScheduler.
areusch
added
the
needs-triage
PRs or issues that need to be investigated by maintainers to find the right assignees to address it
label
Oct 19, 2022
janetsc
added
dev:test-infra
and removed
needs-triage
PRs or issues that need to be investigated by maintainers to find the right assignees to address it
labels
Oct 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/aarch64_frontend_tests/3/pipeline
mark_test_pending
isn't there since we're using aLoadScopeScheduling
instance to serialize some tests: https://github.com/apache/tvm/blob/main/python/tvm/testing/plugin.py#L334. The segfault should just look like any other test error without any pytest internal failures.cc @Mousius @areusch @gigiblender
The text was updated successfully, but these errors were encountered: