You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1bf9426
Browse filesBrowse the repository at this point in the historyBrowse files
CUDA backend: move merge_ptes into backends/cuda/scripts
Stacked on the remap_pte_devices PR, which starts the scripts
directory. merge_ptes is the other standalone CUDA backend tool, so
it belongs there too: backends/cuda/merge_ptes.py moves to
backends/cuda/scripts/merge_ptes.py, and every reference (the CUDA
CI workflow, the CUDA examples README, its tests, and the
:merge_ptes Buck target) now uses
executorch.backends.cuda.scripts.merge_ptes. The old module path is
retired outright; the release-notes: devtools label covers the move.
While moving, both outputs of merge_ptes write through the shared
_scripts_atomic_output writer the remap tool introduced (now its own
:scripts_atomic_output library both tools depend on), so they keep
the inputs' permissions and remove their temp files when a write
fails, instead of leaving 0600 or truncated files behind. The
--output-ptd argument check now runs before any output is written.
Test Plan:
- backends/cuda/tests/test_merge_ptes.py: import strings point at
the new module path, and the CLI test now checks the merged PTE
keeps its first input's permissions with no temp files left. The
suite needs flatc, which this environment lacks, and runs in CI.
- backends/cuda/tests/test_remap_pte_devices.py still passes (17
tests) on this stack.
0 commit comments