don't run linearize().uop tests in get_action_space test (#10766)

* don't run linearize().uop tests in get_action_space test

this part takes 2 minutes in CI and has nothing to do with action space. also not sure if the "for some reason" comment is still relevant

* -n=auto test/models
This commit is contained in:
chenyu
2025-06-10 17:23:53 -04:00
committed by GitHub
parent 52c49dd4f3
commit 5e7ad70aae
2 changed files with 1 additions and 10 deletions
+1 -1
View File
@@ -746,7 +746,7 @@ jobs:
- name: Run real world test
run: METAL=1 python -m pytest -n=auto test/models/test_real_world.py --durations=20
- name: Test models (Metal)
run: METAL=1 python -m pytest test/models -v --durations=20
run: METAL=1 python -m pytest -n=auto test/models -v --durations=20
- name: Run ONNX
run: METAL=1 python -m pytest -n=auto test/external/external_test_onnx_backend.py --durations=20
- name: Test tensor core ops (fake)
-9
View File
@@ -26,15 +26,6 @@ if __name__ == "__main__":
#if not lin.apply_tensor_cores():
lin.apply_opts(hand_coded_optimizations(lin))
test_rebuild(lin)
# confirm linearize can be called twice
uops1 = lin.linearize().uops
uops2 = lin.linearize().uops
for x,y in zip(uops1, uops2):
# for some reason DEFINE_ACC is changing the arg
if x.op != y.op or x.dtype != y.dtype: # or x.arg != y.arg:
uops1.print()
uops2.print()
raise Exception(f"UOPS MISMATCH {x} {y}")
print(len(tactions), len(actions))
print(sorted(list(tactions)))