pytorch - 💡(How to fix) Fix DISABLED LiteInterpreterUpgraderTest.DivTensorV2 [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
pytorch/pytorch#181480Fetched 2026-04-26 05:05:43
View on GitHub
Comments
1
Participants
2
Timeline
11
Reactions
0
Timeline (top)
mentioned ×4subscribed ×4labeled ×2commented ×1

Error Message

Error: open file failed because of errno 2 on fopen: No such file or directory, file path: /__w/pytorch/pytorch/test/cpp/jit/upgrader_models/test_versioned_div_tensor_v2.ptl

Root Cause

This test was disabled because it is failing in CI on all configs (aarch64, py3.10, py3.14, py3.14t, clang18, gcc11, CUDA 13.0).

RAW_BUFFERClick to expand / collapse

Platforms: linux

This test was disabled because it is failing in CI on all configs (aarch64, py3.10, py3.14, py3.14t, clang18, gcc11, CUDA 13.0).

Error: open file failed because of errno 2 on fopen: No such file or directory, file path: /__w/pytorch/pytorch/test/cpp/jit/upgrader_models/test_versioned_div_tensor_v2.ptl

Root cause: test uses FILE (compile-time path) to locate .ptl model files. When test_jit runs from an installed location (site-packages/torch/bin/), the source tree path does not exist.

Also affects: LiteInterpreterTest.GetByteCodeVersion, all FlatbufferUpgraderTest.* tests

Test file path: test/cpp/jit/test_lite_interpreter.cpp

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel @pytorch/jit-oncall

extent analysis

TL;DR

The test failure can be resolved by updating the test to use a path that exists at runtime, rather than relying on the compile-time path.

Guidance

  • Identify the tests that use __FILE__ to locate model files and update them to use a runtime path.
  • Consider using a relative path or an environment variable to locate the model files.
  • Verify that the updated test can find the model files by checking the file path in the test code.
  • Review other tests that may be affected by this issue, such as LiteInterpreterTest.GetByteCodeVersion and FlatbufferUpgraderTest.* tests.

Example

No code example is provided as the issue does not contain sufficient code context.

Notes

The fix may require changes to the test code and potentially the build or installation process to ensure that the model files are accessible at runtime.

Recommendation

Apply workaround: Update the test code to use a runtime path, as the root cause is related to the use of __FILE__ and the test running from an installed location.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING