Skip to content

Commit 4524173

Browse files
danpetrydanpetry
committed
Don't run inductor tests
we're getting an issue with the tests: ValueError: option names {'--shard-id'} already added This might be due to out-of-tree tests; after some debugging attempt I'm removing due to time constraints. The same tests were showing a "RuntimeError: can't create new thread at interpreter shutdown" on python 3.12 This is detailed here python/cpython#115533 From looking at the pytorch code it looks like there's still some polishing of support for 3.12 happening so will consider this an upstream error
1 parent 42be81d commit 4524173

1 file changed

Lines changed: 0 additions & 2 deletions

File tree

‎recipe/meta.yaml‎

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -260,8 +260,6 @@ outputs:
260260
# Note that the `|| true` expression will make the build continue even if the whole script falls over completely
261261
# (for example, in the case of missing imports). There doesn't seem to be a way of making a script exception return
262262
# non-zero but failing tests return zero.
263-
# The inductor tests test the torch.compile backend
264-
- python ./test/run_test.py --inductor --continue-through-error || true # [(gpu_variant or "").startswith("cuda") and (linux and x86_64)]
265263
- python ./test/run_test.py --core --continue-through-error || true
266264
# Run pip check so as to ensure that all pytorch packages are installed
267265
# https://github.com/conda-forge/pytorch-cpu-feedstock/issues/24

0 commit comments

Comments
 (0)