From 41e64c1bb5781f6b0b169d2ee802d764fead17a2 Mon Sep 17 00:00:00 2001 From: Sean McGuire Date: Wed, 1 Jul 2026 17:59:00 -0400 Subject: [PATCH] Use --no-sync in uv run to keep resolved benchmark env uv run re-syncs the venv against the project's declared dependencies, which don't include lsdb/numba, so numpy gets upgraded past numba's supported range (currently to 2.5, breaking the lsdb import). --no-sync keeps the environment resolved by the install step, where numba's numpy pin is respected. Co-Authored-By: Claude Fable 5 --- .github/workflows/benchmark.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/benchmark.yml b/.github/workflows/benchmark.yml index 1fa6128..78070dc 100644 --- a/.github/workflows/benchmark.yml +++ b/.github/workflows/benchmark.yml @@ -29,11 +29,11 @@ jobs: - name: Run benchmark run: > - uv run --python 3.14 pytest benchmarks/test_io.py + uv run --no-sync --python 3.14 pytest benchmarks/test_io.py -k "test_lsdb_single_partition and local" --lbench - name: Run crossmatch benchmarks run: > - uv run --python 3.14 pytest benchmarks/test_crossmatch.py + uv run --no-sync --python 3.14 pytest benchmarks/test_crossmatch.py --lbench