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

[Flaky Test] python-integration-contrib-test_ethosu-shard-5-ctypes failed on PR with unrelated changes #12933

Closed
janetsc opened this issue Sep 28, 2022 · 1 comment

Comments

@janetsc
Copy link
Collaborator

janetsc commented Sep 28, 2022

I'm seeing a CI failure on python-integration-contrib-test_ethosu-shard-5-ctypes: tests/python/contrib/test_ethosu for Cortex-M5 on this PR: https://ci.tlcpack.ai/blue/organizations/jenkins/tvm/detail/PR-12918/2/pipeline.

A previous run was successful, and the only thing I changed was specific to Hexagon.

Full logs are here: https://ci.tlcpack.ai/blue/rest/organizations/jenkins/pipelines/tvm/branches/PR-12918/runs/2/nodes/481/steps/1328/log/?start=0.

@janetsc janetsc added the needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it label Sep 28, 2022
@driazati driazati added test: flaky and removed needs-triage PRs or issues that need to be investigated by maintainers to find the right assignees to address it labels Sep 28, 2022
@driazati driazati changed the title [CI Problem] python-integration-contrib-test_ethosu-shard-5-ctypes failed on PR with unrelated changes [Flaky Test] python-integration-contrib-test_ethosu-shard-5-ctypes failed on PR with unrelated changes Sep 28, 2022
driazati added a commit to driazati/tvm that referenced this issue Sep 30, 2022
These are all segfaulting in main (see apache#12955, apache#12933, and apache#12841) so
they need to be skipped until a fix is merged.
@driazati
Copy link
Member

thanks for reporting! looks like we've seen this before (#12841) so I filed a PR to disable this test. Closing this issue for now to consolidate on #12841

driazati added a commit to driazati/tvm that referenced this issue Sep 30, 2022
These are all segfaulting in main (see apache#12955, apache#12933, and apache#12841) so
they need to be skipped until a fix is merged.
driazati added a commit to driazati/tvm that referenced this issue Sep 30, 2022
These are all segfaulting in main (see apache#12955, apache#12933, and apache#12841) so
they need to be skipped until a fix is merged.
driazati added a commit to driazati/tvm that referenced this issue Sep 30, 2022
These are all segfaulting in main (see apache#12955, apache#12933, and apache#12841) so
they need to be skipped until a fix is merged.
driazati added a commit to driazati/tvm that referenced this issue Sep 30, 2022
These are all segfaulting in main (see apache#12955, apache#12933, and apache#12841) so
they need to be skipped until a fix is merged.
driazati added a commit to driazati/tvm that referenced this issue Oct 3, 2022
These are all segfaulting in main (see apache#12955, apache#12933, and apache#12841) so
they need to be skipped until a fix is merged.
junrushao pushed a commit that referenced this issue Oct 6, 2022
These are all segfaulting in main (see #12955, #12933, and #12841) so
they need to be skipped until a fix is merged.

Co-authored-by: driazati <driazati@users.noreply.github.com>
xinetzone pushed a commit to daobook/tvm that referenced this issue Nov 25, 2022
These are all segfaulting in main (see apache#12955, apache#12933, and apache#12841) so
they need to be skipped until a fix is merged.

Co-authored-by: driazati <driazati@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants