[rpms/python-trimesh] f44: Do not run BoundsTest::test_obb_mesh_large at all

[rpms/python-trimesh] f44: Do not run BoundsTest::test_obb_mesh_large at all

[Benjamin A. Beasley]

            A new commit has been pushed.

            Repo   : rpms/python-trimesh
            Branch : f44
            Commit : 2122b020089819d20b65776bfd9e42c66803b179
            Author : Benjamin A. Beasley <code@musicinmybrain.net>
            Date   : 2026-07-23T23:20:33+01:00
            Stats  : +5/-4 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-trimesh/c/2122b020089819d20b65776bfd9e42c66803b179?branch=f44

            Log:
            Do not run BoundsTest::test_obb_mesh_large at all

It is purely a performance check, under assumptions that may not apply
downstream.

---
diff --git a/python-trimesh.spec b/python-trimesh.spec
index 2e9c44d..a59d9cb 100644
--- a/python-trimesh.spec
+++ b/python-trimesh.spec
@@ -303,15 +303,16 @@ deselect="${deselect-} --deselect=tests/test_color.py::test_data_model"
 k="${k-}${k+ and }not test_contains_cavity"
 %endif
 
-# This test fails if it doesn’t finish within 30 seconds, and executing it in
-# parallel with other tests tends to slow it down too much. We exclude it here,
-# then run it serially on its own.
+# This test fails if it doesn’t finish within 60 seconds, and executing it in
+# parallel with other tests tends to slow it down too much. Furthermore, the
+# only assertion in the test is the one on execution time, and builder hardware
+# may be quite different (and potentially slower) than what upstream is using
+# for development and CI, so it provides no real value downstream.
 # tests/test_bounds.py::BoundsTest::test_obb_mesh_large
 k="${k-}${k+ and }not (BoundsTest and test_obb_mesh_large)"
 
 export PYTHONPATH="${PWD}/_stub:%{buildroot}%{python3_sitelib}"
 %pytest -v -k "${k-}" -n auto ${deselect-}
-%pytest -v -k '(BoundsTest and test_obb_mesh_large)'
 
 
 %files -n python3-trimesh -f %{pyproject_files}