Skip to content

🐍 Geometric Computer Vision Library for Spatial AI

ci: replace PyTorch 2.14 with 2.15 in the test suite (#6380)

Dmytro Mishkinb7dc221ad571
diff --git a/.github/workflows/pr_test_cpu.yml b/.github/workflows/pr_test_cpu.yml
index 2237e80b4..d11713f7b 100644
--- a/.github/workflows/pr_test_cpu.yml
+++ b/.github/workflows/pr_test_cpu.yml
@@ -120,7 +120,7 @@ jobs:
# - ubuntu 3.12 / torch 2.9.1 (float32): the first release on which `torch.onnx.export`,
# and with it `to_onnx`, defaults to the dynamo exporter. Its torch.export specializes
# differently from 2.14's: a DexiNed export ran only at the traced batch size (#6066).
- # - ubuntu 3.11 / torch 2.14.0 (float32, float64): the oldest Python on the newest torch,
+ # - ubuntu 3.11 / torch 2.15.0 (float32, float64): the oldest Python on the newest torch,
# so every Python and torch pin still gets a full-suite run in both dtypes on Linux.
# - windows-latest float64: Windows-only failures (path handling, the eager RNG audit)
# showed up on every Windows leg, and this one caught all of them.
@@ -145,19 +145,19 @@ jobs:
- os: ubuntu-latest
pytorch-dtype: "float32"
python-version: "3.11"
- pytorch-version: "2.14.0"
+ pytorch-version: "2.15.0"
- os: ubuntu-latest
pytorch-dtype: "float64"
python-version: "3.11"
- pytorch-version: "2.14.0"
+ pytorch-version: "2.15.0"
- os: windows-latest
pytorch-dtype: "float64"
python-version: "3.13"
- pytorch-version: "2.14.0"
+ pytorch-version: "2.15.0"
- os: macos-latest
pytorch-dtype: "float32"
python-version: "3.13"
- pytorch-version: "2.14.0"
+ pytorch-version: "2.15.0"
uses: ./.github/workflows/tests.yml
with:
@@ -181,7 +181,7 @@ jobs:
with:
os: ubuntu-latest
python-version: '["3.11"]'
- pytorch-version: '["2.14.0"]'
+ pytorch-version: '["2.15.0"]'
pytorch-dtype: ${{ matrix.pytorch-dtype }}
known-failure-profile: cpu-${{ matrix.pytorch-dtype }}
# A whole leg takes ~6m, so no single test comes near these limits. A native float16 kernel
@@ -208,7 +208,7 @@ jobs:
with:
os: ubuntu-latest
python-version: '["3.11"]'
- pytorch-version: '["2.14.0"]'
+ pytorch-version: '["2.15.0"]'
pytorch-dtype: float32
optimizer: inductor
pytest-extra: 'tests/augmentation tests/enhance tests/feature tests/filters tests/color tests/geometry tests/losses tests/morphology tests/models tests/core tests/utils -k "dynamo or compile"'
@@ -220,10 +220,14 @@ jobs:
# Single blocking MPS leg: newest Python, float32, on an Apple-silicon image.
# The exact known-failure baseline is pinned as strict xfails: a new failure,
- # changed failure, skipped pin, or fixed pin makes the job red and requires review. The
- # torch pin tracks the newest pin of the CPU matrix so the leg resolves the locked
- # dependency set; changing it means re-recording the manifest in the same change, because
- # a release that adds MPS kernels turns recorded failures into strict XPASSes.
+ # changed failure, skipped pin, or fixed pin makes the job red and requires review.
+ # Changing the torch pin means re-recording the manifest in the same change, because a
+ # release that adds MPS kernels turns recorded failures into strict XPASSes.
+ #
+ # The torch pin stays at 2.14.0, behind the CPU matrix (#6390): torch 2.15 uses only a GPU
+ # in MTLGPUFamilyApple7, and the paravirtual GPU of every GitHub-hosted arm64 image reports
+ # Mac2 and Common3 only, so on 2.15 `Verify MPS device` finds no MPS device. Move the pin
+ # only to a release that accepts this GPU again, or together with a runner that has one.
#
# The image is pinned to macos-15 rather than macos-latest, and that is not cosmetic.
# macos-latest is macos-26-arm64, whose GPU is paravirtualized; on macOS 26 torch 2.14
@@ -259,7 +263,7 @@ jobs:
# ONNX conformance (#5819): every promised operator of the packages this PR can affect must export with the dynamo
# exporter and match eager in onnxruntime, and a legacy export that succeeds must not give wrong values. The
# `changes` job maps the changed paths to the packages they belong to plus every package that imports them
- # (.github/scripts/conformance_packages.py); the whole set runs on main twice a day on torch 2.9.1 and 2.14.0
+ # (.github/scripts/conformance_packages.py); the whole set runs on main twice a day on torch 2.9.1 and 2.15.0
# (scheduled_test_cpu.yml). No promised operator needs pretrained weights, so the job does not wait for `pre-tests`
# and also runs when only the survey or its snapshot under docs/ changed.
onnx-conformance:
@@ -269,7 +273,7 @@ jobs:
with:
os: ubuntu-latest
python-version: '["3.11"]'
- pytorch-version: '["2.14.0"]'
+ pytorch-version: '["2.15.0"]'
pytorch-dtype: float32
test-path: tests/onnx/test_conformance.py
# pytest-timeout fails a case that runs past 10 min and names it, rather than the job timeout ending the run
@@ -286,7 +290,7 @@ jobs:
with:
os: ubuntu-latest
python-version: '["3.11"]'
- pytorch-version: '["2.14.0"]'
+ pytorch-version: '["2.15.0"]'
pytorch-dtype: float32
test-path: tests/test_inductor_conformance.py
# pytest-timeout fails a case that runs past 10 min and names it, rather than the job timeout ending the run
diff --git a/.github/workflows/scheduled_test_cpu.yml b/.github/workflows/scheduled_test_cpu.yml
index 88d3cfca0..3776aad55 100644
--- a/.github/workflows/scheduled_test_cpu.yml
+++ b/.github/workflows/scheduled_test_cpu.yml
@@ -164,7 +164,7 @@ jobs:
matrix:
pytorch-dtype: ["float32", "float64"]
python-version: ["3.11", "3.12", "3.13"]
- pytorch-version: ["2.5.1", "2.6.0", "2.9.1", "2.14.0"]
+ pytorch-version: ["2.5.1", "2.6.0", "2.9.1", "2.15.0"]
uses: ./.github/workflows/tests.yml
with:
@@ -189,7 +189,7 @@ jobs:
with:
os: ubuntu-latest
python-version: '["3.11"]'
- pytorch-version: '["2.14.0"]'
+ pytorch-version: '["2.15.0"]'
pytorch-dtype: ${{ matrix.pytorch-dtype }}
known-failure-profile: cpu-${{ matrix.pytorch-dtype }}
# Same hang guard as the PR half-precision job (#5493).
@@ -200,7 +200,7 @@ jobs:
model-weights-${{ needs.pre-tests.outputs.hash }}
model-weights-
- # ONNX conformance (#5819) of every promised operator on both enforced torch releases; the PR run covers 2.14.0
+ # ONNX conformance (#5819) of every promised operator on both enforced torch releases; the PR run covers 2.15.0
# for the packages a change touches and the packages that import them.
onnx-conformance:
needs: [check-skip]
@@ -209,14 +209,14 @@ jobs:
with:
os: ubuntu-latest
python-version: '["3.11"]'
- pytorch-version: '["2.9.1", "2.14.0"]'
+ pytorch-version: '["2.9.1", "2.15.0"]'
pytorch-dtype: float32
test-path: tests/onnx/test_conformance.py
# pytest-timeout fails a case that runs past 10 min and names it, rather than the job timeout ending the run
pytest-extra: --onnx-conformance=all --timeout=600
# torch.compile conformance (#5819) of every promised operator on both enforced torch releases; the PR run covers
- # 2.14.0 for the packages a change touches and the packages that import them.
+ # 2.15.0 for the packages a change touches and the packages that import them.
compile-conformance:
needs: [check-skip]
if: needs.check-skip.outputs.should-skip == 'false'
@@ -224,7 +224,7 @@ jobs:
with:
os: ubuntu-latest
python-version: '["3.11"]'
- pytorch-version: '["2.9.1", "2.14.0"]'
+ pytorch-version: '["2.9.1", "2.15.0"]'
pytorch-dtype: float32
test-path: tests/test_inductor_conformance.py
# pytest-timeout fails a case that runs past 10 min and names it, rather than the job timeout ending the run
@@ -239,7 +239,7 @@ jobs:
os: ["windows-latest"]
pytorch-dtype: ["float32", "float64"]
python-version: ["3.11", "3.12", "3.13"]
- pytorch-version: ["2.5.1", "2.9.1", "2.14.0"]
+ pytorch-version: ["2.5.1", "2.9.1", "2.15.0"]
exclude:
# PyTorch 2.5.1 doesn't have wheels for Python 3.13 on Windows
- python-version: "3.13"
@@ -286,7 +286,7 @@ jobs:
matrix:
pytorch-dtype: ["float32", "float64"]
python-version: ["3.11", "3.12", "3.13"]
- pytorch-version: ["2.5.1", "2.9.1", "2.14.0"]
+ pytorch-version: ["2.5.1", "2.9.1", "2.15.0"]
exclude:
# PyTorch 2.5.1 doesn't have wheels for Python 3.13 on macOS
- python-version: "3.13"
diff --git a/.github/workflows/tests.yml b/.github/workflows/tests.yml
index b2bfaa133..c521894f9 100644
--- a/.github/workflows/tests.yml
+++ b/.github/workflows/tests.yml
@@ -8,7 +8,7 @@ on:
pytorch-version:
required: false
type: string
- default: '["2.14.0"]'
+ default: '["2.15.0"]'
torch-channel:
# "pinned" (default) installs exactly the pytorch-version matrix value, byte-identical
# to prior behavior. "stable" ignores pytorch-version for the install step itself and
diff --git a/.github/workflows/upstream_probe.yml b/.github/workflows/upstream_probe.yml
index 98c0c2f32..c5eb8c771 100644
--- a/.github/workflows/upstream_probe.yml
+++ b/.github/workflows/upstream_probe.yml
@@ -78,7 +78,7 @@ jobs:
with:
os: ubuntu-latest
python-version: '["3.13"]'
- pytorch-version: '["2.14.0"]'
+ pytorch-version: '["2.15.0"]'
torch-channel: stable
pytorch-dtype: float32
cache-path: weights/
@@ -93,7 +93,7 @@ jobs:
with:
os: ubuntu-latest
python-version: '["3.13"]'
- pytorch-version: '["2.14.0"]'
+ pytorch-version: '["2.15.0"]'
torch-channel: stable
pytorch-dtype: float64
cache-path: weights/
@@ -108,7 +108,7 @@ jobs:
with:
os: ubuntu-latest
python-version: '["3.11"]'
- pytorch-version: '["2.14.0"]'
+ pytorch-version: '["2.15.0"]'
torch-channel: stable
pytorch-dtype: float16
known-failure-profile: cpu-float16
@@ -125,7 +125,7 @@ jobs:
with:
os: ubuntu-latest
python-version: '["3.11"]'
- pytorch-version: '["2.14.0"]'
+ pytorch-version: '["2.15.0"]'
torch-channel: stable
pytorch-dtype: bfloat16
known-failure-profile: cpu-bfloat16
@@ -142,7 +142,7 @@ jobs:
with:
os: ubuntu-latest
python-version: '["3.14"]'
- pytorch-version: '["2.14.0"]'
+ pytorch-version: '["2.15.0"]'
torch-channel: stable
pytorch-dtype: float32
cache-path: weights/
diff --git a/README.md b/README.md
index f3dfb7d1c..47ce0f17e 100644
--- a/README.md
+++ b/README.md
@@ -131,7 +131,7 @@ Leverage pre-trained AI models optimized for a variety of vision tasks, all with
The module table below counts entries in the Linux CPU known-failure manifests
([`cpu_float16.txt`](testing/half_precision_xfails/cpu_float16.txt),
-[`cpu_bfloat16.txt`](testing/half_precision_xfails/cpu_bfloat16.txt)), pinned to Python 3.11 and PyTorch 2.14.0.
+[`cpu_bfloat16.txt`](testing/half_precision_xfails/cpu_bfloat16.txt)), pinned to Python 3.11 and PyTorch 2.15.0.
There are **243 float16 and 256 bfloat16 recorded failures**. These are parametrized test cases, not counts of
unsupported functions. The remaining work is tracked in [#4153](https://github.com/kornia/kornia/issues/4153).
No CI job covers CUDA or MPS half precision; CPU results do not establish support on those backends.
diff --git a/TESTING.md b/TESTING.md
index 8ee7b9376..3b1bbfc50 100644
--- a/TESTING.md
+++ b/TESTING.md
@@ -96,11 +96,11 @@ pixi run test-module tests/onnx/test_conformance.py --onnx-conformance=all
pixi run test-module tests/onnx/test_conformance.py --onnx-conformance=geometry,color
```
-The run takes minutes, so it is opt-in. Pull requests run it on torch 2.14.0 for the packages their changes reach
+The run takes minutes, so it is opt-in. Pull requests run it on torch 2.15.0 for the packages their changes reach
(`.github/scripts/conformance_packages.py onnx`: a changed module selects its stable-core package and every
stable-core package with a module that imports it, directly or not; `kornia/core`, `kornia/utils`, `kornia/onnx`, the
survey and its snapshot, the stability page, the test and its support, and the dependency pins select `all`); the
-scheduled run on `main` checks `all` on torch 2.9.1 and 2.14.0. No promised case needs pretrained weights, and the test
+scheduled run on `main` checks `all` on torch 2.9.1 and 2.15.0. No promised case needs pretrained weights, and the test
never downloads.
Known failures are strict xfails in `testing/known_failure_xfails/onnx_conformance_torch<major>.<minor>.txt`, one
@@ -135,9 +135,9 @@ pixi run test-module tests/test_inductor_conformance.py --compile-conformance=co
It has its own option and does not read `KORNIA_TEST_OPTIMIZER`, and its tests are named after inductor because the
root `conftest.py` drops tests whose name contains `compile` or `dynamo` when that variable is unset. Inductor needs a
-C++ compiler; onnx and onnxruntime are not needed. Pull requests run it on torch 2.14.0 for the packages
+C++ compiler; onnx and onnxruntime are not needed. Pull requests run it on torch 2.15.0 for the packages
`.github/scripts/conformance_packages.py compile` selects (the same mapping as the ONNX job, with this test file and
-its manifests in place of the ONNX ones); the scheduled run on `main` checks `all` on torch 2.9.1 and 2.14.0. Both
+its manifests in place of the ONNX ones); the scheduled run on `main` checks `all` on torch 2.9.1 and 2.15.0. Both
conformance jobs run with `--timeout=600`.
---
@@ -411,7 +411,7 @@ process before they can raise.
The `padding_mode="border"` issue in `F.grid_sample` (2D) is worked around in the implementation (`kornia/feature/laf.py`) by clamping the sampling grid to the outermost pixel *centers*, at `Β±(1 - 1/size)`, and using `padding_mode="zeros"`, which is exactly equivalent. Clamping to `[-1, 1]` is not: with `align_corners=False` that is the outer edge of the border pixel, where bilinear sampling blends it with the zero padding.
-**CI coverage.** Pull-request CI runs one blocking MPS leg (`tests-mps` in `.github/workflows/pr_test_cpu.yml`): the newest Python and the newest pinned PyTorch, `float32`, on the GitHub-hosted **`macos-15`** Apple-silicon image. The image is pinned deliberately. `macos-latest` is `macos-26-arm64`, whose GPU is paravirtualized, and on macOS 26 torch 2.14 emits Metal 4 `mpp::tensor_ops::matmul2d` cooperative-tensor shaders that this virtual GPU cannot compile β€” one specialization failed 664 tests across every subpackage, since `linalg.inv`, `linalg.solve`, `inv_ex`, `lu_factor_ex` and `F.conv3d` all route through it. The defect is the *virtual* GPU, not macOS 26: a physical M1 on macOS 26.5 compiled those shaders in the #4202 comparison. macOS 15 is Metal 3 and takes the older kernel path, which is the path that happens to work on the runner fleet. Two consequences worth knowing: no job in this repository now exercises the Metal 4 path that users on current macOS actually run, and when GitHub retires the `macos-15` image this leg stops scheduling and `collector` goes red with no fallback. Re-test `macos-latest` once upstream guards those kernels by device capability; `macos-14` segfaults inside MPS kernels and must never be used. The comparison is recorded in [#4159](https://github.com/kornia/kornia/issues/4159#issuecomment-5532655834). The exact known-failure baseline lives in `testing/known_failure_xfails/mps_float32.txt`. `--xfail-known-failures` applies the manifest's entries as strict xfails with their exact exception types. A new failure, a different exception, a skipped recorded test, or a fixed test therefore makes CI red.
+**CI coverage.** Pull-request CI runs one blocking MPS leg (`tests-mps` in `.github/workflows/pr_test_cpu.yml`): the newest Python and PyTorch 2.14.0, `float32`, on the GitHub-hosted **`macos-15`** Apple-silicon image. PyTorch stays one release behind the CPU matrix: torch 2.15 uses only a GPU in `MTLGPUFamilyApple7`, and the paravirtual GPU of every GitHub-hosted arm64 image does not report that family, so on 2.15 the leg finds no MPS device ([#6390](https://github.com/kornia/kornia/issues/6390)). The image is pinned deliberately. `macos-latest` is `macos-26-arm64`, whose GPU is paravirtualized, and on macOS 26 torch 2.14 emits Metal 4 `mpp::tensor_ops::matmul2d` cooperative-tensor shaders that this virtual GPU cannot compile β€” one specialization failed 664 tests across every subpackage, since `linalg.inv`, `linalg.solve`, `inv_ex`, `lu_factor_ex` and `F.conv3d` all route through it. The defect is the *virtual* GPU, not macOS 26: a physical M1 on macOS 26.5 compiled those shaders in the #4202 comparison. macOS 15 is Metal 3 and takes the older kernel path, which is the path that happens to work on the runner fleet. Two consequences worth knowing: no job in this repository now exercises the Metal 4 path that users on current macOS actually run, and when GitHub retires the `macos-15` image this leg stops scheduling and `collector` goes red with no fallback. Re-test `macos-latest` once upstream guards those kernels by device capability; `macos-14` segfaults inside MPS kernels and must never be used. The comparison is recorded in [#4159](https://github.com/kornia/kornia/issues/4159#issuecomment-5532655834). The exact known-failure baseline lives in `testing/known_failure_xfails/mps_float32.txt`. `--xfail-known-failures` applies the manifest's entries as strict xfails with their exact exception types. A new failure, a different exception, a skipped recorded test, or a fixed test therefore makes CI red.
Run the identical contract locally with `pixi run test-mps`. `PYTORCH_ENABLE_MPS_FALLBACK=1` silently routes missing MPS kernels to the CPU and invalidates the baseline, so unset it first. The manifest is a full-suite contract and is not intended for `-k` or partial-directory runs; use `pixi run test-module ... --device=mps --dtype=float32` for focused diagnosis without the manifest. "Full suite" means the suite as an `mps`-only run collects it: tests marked `device_agnostic` are deselected there and covered by the CPU jobs, so they never appear in the manifest.
diff --git a/testing/conformance_promise.py b/testing/conformance_promise.py
index 8aff1853b..f5939b97f 100644
--- a/testing/conformance_promise.py
+++ b/testing/conformance_promise.py
@@ -80,8 +80,8 @@ CASE_TEST_CHECKS = {
# Where CI checks the promises: the onnx-conformance and compile-conformance jobs of scheduled_test_cpu.yml (on main,
# CI_RUNS_PER_DAY times a day) and of pr_test_cpu.yml (pull requests). tests/test_generate_export_support.py checks
# these against the workflows, and the support statement renders them.
-CI_TORCH_SCHEDULED = ("2.9.1", "2.14.0")
-CI_TORCH_PULL_REQUEST = ("2.14.0",)
+CI_TORCH_SCHEDULED = ("2.9.1", "2.15.0")
+CI_TORCH_PULL_REQUEST = ("2.15.0",)
CI_RUNS_PER_DAY = 2
CI_PYTHON = "3.11"
CI_OS = "ubuntu-latest"
diff --git a/testing/half_precision_xfails/cpu_bfloat16.txt b/testing/half_precision_xfails/cpu_bfloat16.txt
index c9785049f..bfe460e19 100644
--- a/testing/half_precision_xfails/cpu_bfloat16.txt
+++ b/testing/half_precision_xfails/cpu_bfloat16.txt
@@ -1,7 +1,7 @@
# known-failure-schema: 1
# profile: cpu-bfloat16
# python: 3.11
-# pytorch: 2.14.0
+# pytorch: 2.15.0
# os: Linux
# arch: x86_64
# seed-scheme: sha256-nodeid-v1
diff --git a/testing/half_precision_xfails/cpu_float16.txt b/testing/half_precision_xfails/cpu_float16.txt
index bc1e0a1e7..aa4e463f1 100644
--- a/testing/half_precision_xfails/cpu_float16.txt
+++ b/testing/half_precision_xfails/cpu_float16.txt
@@ -1,7 +1,7 @@
# known-failure-schema: 1
# profile: cpu-float16
# python: 3.11
-# pytorch: 2.14.0
+# pytorch: 2.15.0
# os: Linux
# arch: x86_64
# seed-scheme: sha256-nodeid-v1
diff --git a/testing/known_failure_xfails/compile_conformance_torch2.15.txt b/testing/known_failure_xfails/compile_conformance_torch2.15.txt
new file mode 100644
index 000000000..2ac231d15
--- /dev/null
+++ b/testing/known_failure_xfails/compile_conformance_torch2.15.txt
@@ -0,0 +1,8 @@
+# Strict known-failure baseline of tests/test_inductor_conformance.py on torch 2.15.0 (CPU float32, Python 3.11):
+# promised operators that do not compile with torch.compile(fullgraph=True) and the inductor backend, or whose
+# compiled result differs from eager (#5819).
+# Remove an entry when its case passes (a strict XPASS fails the run). A new failure of a promised operator is a
+# regression to fix; add it only with a comment naming its own tracking issue.
+# Entries of packages a run does not select are not checked; every node ID must name a promised case.
+# Format: <exact exception type>\t<pytest node ID>. The type names the kind of failure (testing.conformance
+# STATUS_EXCEPTIONS): AssertionError a wrong result, RuntimeError a failed compile, ValueError a failed eager run.
diff --git a/testing/known_failure_xfails/onnx_conformance_torch2.15.txt b/testing/known_failure_xfails/onnx_conformance_torch2.15.txt
new file mode 100644
index 000000000..b3fd3eb3d
--- /dev/null
+++ b/testing/known_failure_xfails/onnx_conformance_torch2.15.txt
@@ -0,0 +1,9 @@
+# Strict known-failure baseline of tests/onnx/test_conformance.py on torch 2.15.0 (CPU float32, Python 3.11, the
+# locked onnx / onnxruntime / onnxscript): promised operators that do not export with the dynamo exporter and match
+# eager, or whose legacy export succeeds with a wrong result (#5819).
+# Remove an entry when its case passes (a strict XPASS fails the run). A new failure of a promised operator is a
+# regression to fix; add it only with a comment naming its own tracking issue.
+# Entries of packages a run does not select are not checked; every node ID must name a promised case.
+# Format: <exact exception type>\t<pytest node ID>. The type names the kind of failure (testing.conformance
+# STATUS_EXCEPTIONS): AssertionError a wrong result, RuntimeError a failed export, checker or onnxruntime run,
+# ValueError a failed eager run.
diff --git a/tests/models/test_sam_onnx.py b/tests/models/test_sam_onnx.py
index 0bed49827..3337e3b3a 100644
--- a/tests/models/test_sam_onnx.py
+++ b/tests/models/test_sam_onnx.py
@@ -43,16 +43,16 @@ def test_sam_has_to_onnx():
@pytest.mark.timeout(120)
@pytest.mark.xfail(
- torch_version_ge(2, 14) and torch_version_lt(2, 15, 0),
+ torch_version_ge(2, 14) and torch_version_lt(2, 16, 0),
reason=(
- "torch 2.14's dynamo ONNX exporter cannot translate aten.mul.Scalar for this graph in the CPU "
- "build (the CUDA build exports it): DispatchError 'No decompositions registered for the "
+ "the dynamo ONNX exporter of torch 2.14 and 2.15 cannot translate aten.mul.Scalar for this graph in "
+ "the CPU build (the 2.14 CUDA build exports it): DispatchError 'No decompositions registered for the "
"real-valued input'; not yet reported upstream"
),
raises=torch.onnx.OnnxExporterError,
- # Strict on the CPU builds, where an upstream fix inside 2.14.x must announce itself as an XPASS failure rather
- # than sit silently until the 2.15 bound expires. A CUDA build of 2.14.0 exports this graph (2.14.0+cu130 on
- # Linux), so there the marker is not strict.
+ # Strict on the CPU builds, where an upstream fix inside 2.14.x or 2.15.x must announce itself as an XPASS failure
+ # rather than sit silently until the 2.16 bound expires. A CUDA build of 2.14.0 exports this graph (2.14.0+cu130
+ # on Linux), so there the marker is not strict.
strict=torch.version.cuda is None,
)
def test_sam_encoder_to_onnx(tmp_path):
diff --git a/tests/test_half_precision_ci.py b/tests/test_half_precision_ci.py
index b906617be..fd713cfac 100644
--- a/tests/test_half_precision_ci.py
+++ b/tests/test_half_precision_ci.py
@@ -917,6 +917,13 @@ def test_upstream_probe_floor_is_consistent_across_jobs() -> None:
}
assert len(set(floors.values())) == 1, floors
+ root = Path(project_conftest.__file__).parent
+ blocking = (root / ".github" / "workflows" / "pr_test_cpu.yml").read_text(encoding="utf-8")
+ # Both the matrix entries (`pytorch-version: "2.15.0"`) and the JSON pins of single jobs (`'["2.15.0"]'`).
+ pins = re.findall(r"\n\s+pytorch-version: (.+)", blocking)
+ pinned = [version for pin in pins for version in re.findall(r'"(\d+\.\d+\.\d+)"', pin)]
+ latest = max(pinned, key=lambda version: tuple(map(int, version.split("."))))
+ assert set(floors.values()) == {latest}, floors
def test_upstream_probe_record_jobs_match_the_blocking_python() -> None: