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 7d43a53
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 and breaking-change
labels cover the move.
While moving, both outputs of merge_ptes write through the shared
scripts/_atomic_output writer from the base PR's
:scripts_atomic_output library -- the PTD first, so a failed copy
leaves the existing output PTE untouched -- 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 (now also registered as a
Buck python_unittest): import strings point at the new module
path, the CLI test checks PTE and PTD output permissions against
distinctive input modes, --output-ptd without --input-ptd writes
nothing, and a failed PTD copy leaves neither output nor temp
files. The suite needs flatc, which this environment lacks, and
runs in CI.
- backends/cuda/tests/test_remap_pte_devices.py still passes (20
tests) on this stack.
0 commit comments