Skip to content

L4T Orin test_program.py::test_cuda_gdb_shows_nvrtc_debug_source_lines failures #2693

Description

@rwgk

These are from automatic testing against CTK 13.3 run by @nikshayshrivastava

@nikshayshrivastava has full log files.

The previous run, with Sat Aug 22 12:48:14 AM IST 2026 had only 3 failures, as already reported under issue #2527.

This is the first run with 4 failures:

cuda-python Test Report
=======================
Board  : local_l4t
Date   : Sun Aug 23 12:48:06 AM IST 2026
Result : FAILED

--- Suite Results ---
cuda_pathfinder  : 1327 passed, 0 failed, 1 skipped, 0 xfailed
cuda_bindings    : 452 passed, 0 failed, 38 skipped, 0 xfailed
cuda_core        : 3618 passed, 4 failed, 487 skipped, 2 xfailed

Total            : 5397 passed, 4 failed, 2 xfailed
Note             : xfailed = expected failures (known issues, marked xfail in tests)

--- Failures ---
FAILED cuda_core/tests/graph/test_graph_memory_resource.py::test_graph_alloc_with_output[global] - RuntimeError: Instantiation failed for an unexpected reason which is described in the return value of the function.
FAILED cuda_core/tests/graph/test_graph_memory_resource.py::test_graph_alloc_with_output[relaxed] - RuntimeError: Instantiation failed for an unexpected reason which is described in the return value of the function.
FAILED cuda_core/tests/graph/test_graph_memory_resource.py::test_graph_alloc_with_output[thread_local] - RuntimeError: Instantiation failed for an unexpected reason which is described in the return value of the function.
FAILED cuda_core/tests/test_program.py::test_cuda_gdb_shows_nvrtc_debug_source_lines - AssertionError: [Thread debugging using libthread_db enabled]

The new failure is:

FAILED cuda_core/tests/test_program.py::test_cuda_gdb_shows_nvrtc_debug_source_lines - AssertionError: [Thread debugging using libthread_db enabled]

codex gpt-5.6-sol ultra found:

The culprit is almost certainly PR #2679, merged between the Aug 22 and Aug 23 runs. It introduced the exact failing test at cuda_core/tests/test_program.py:1095, its helper, and the NVRTC source-materialization behavior being tested.

Confidence is very high that #2679 introduced the fourth test failure. The abbreviated assertion is insufficient to determine whether the implementation is broken on L4T or the new test needs an L4T-specific skip/probe.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions