Skip to content

DISABLED test_relative_import (__main__.ReproTests) #156679

@pytorch-bot

Description

@pytorch-bot

Platforms: linux, rocm, slow

This test was disabled because it is failing in CI. See recent examples and the most recent trunk workflow logs.

Over the past 3 hours, it has been determined flaky in 12 workflow(s) with 24 failures and 12 successes.

Debugging instructions (after clicking on the recent samples link):
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:

  1. Click on the workflow logs linked above
  2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
  3. Grep for test_relative_import
  4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
Sample error message
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/dynamo/test_repros.py", line 2482, in test_relative_import
    fn(x)
  File "/var/lib/jenkins/workspace/test/dynamo/test_repros.py", line 2479, in fn
    return x * 2 * tensor_for_import_testing
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu!

To execute this test, run the following from the base repo dir:
    python test/dynamo/test_repros.py ReproTests.test_relative_import

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0

Test file path: dynamo/test_repros.py

For all disabled tests (by GitHub issue), see https://hud.pytorch.org/disabled.

cc @clee2000 @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @chauhang @amjames

Metadata

Metadata

Assignees

No one assigned

    Labels

    module: dynamomodule: flaky-testsProblem is a flaky test in CIoncall: pt2skippedDenotes a (flaky) test currently skipped in CI.triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate module

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions