8000 [Upstream Triton] AssertionError: expected to fail, but actually passed ```test_unbacked_reduction_cpu``` · Issue #154217 · pytorch/pytorch · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content 8000
[Upstream Triton] AssertionError: expected to fail, but actually passed test_unbacked_reduction_cpu #154217
Closed
@iupaikov-amd

Description

@iupaikov-amd

🐛 Describe the bug

Testing ToT triton before release/2.8 to assess the issues.

This test fails locally on amd gpus and is not confirmed to be common for cuda.

Affected tests: 1

reproducer: python test/inductor/test_torchinductor_dynamic_shapes.py TestInductorDynamicCPU.test_unbacked_reduction_cpu

error message:

{'message': 'AssertionError: expected to fail, but actually passed\n\nTo execute this test, run the following from the base repo dir:\n    python test/inductor/test_torchinductor_dynamic_shapes.py TestInductorDynamicCPU.test_unbacked_reduction_cpu\n\nThis message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0', 'text': 'Traceback (most recent call last):\n  File "/tmp/pytorch/test/inductor/test_torchinductor_dynamic_shapes.py", line 498, in test_unbacked_reduction\n    self.fail("expected to fail, but actually passed")\n  File "/opt/conda/envs/py_3.10/lib/python3.10/unittest/case.py", line 675, in fail\n    raise self.failureException(msg)\nAssertionError: expected to fail, but actually passed\n\nTo execute this test, run the following from the base repo dir:\n    python test/inductor/test_torchinductor_dynamic_shapes.py TestInductorDynamicCPU.test_unbacked_reduction_cpu\n\nThis message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0'}

Versions

upstream pytorch + triton commit: triton-lang/triton@2ec711b

cc @chauhang @penguinwu @bertmaher @int3 @davidberard98 @nmacchioni @chenyang78 @embg @peterbell10 @aakhundov

Metadata

Metadata

Assignees

No one assigned

    Labels

    oncall: pt2triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleupstream tritonUpstream Triton Issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0