mirror of
https://github.com/azaion/gps-denied-onboard.git
synced 2026-06-22 17:11:14 +00:00
chore: WIP pre-implement
Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
# D-CROSS-CVE-1 opencv-python pin deferred — gtsam/numpy ABI block
|
||||
|
||||
**Recorded**: 2026-05-11T02:55+03:00 (Europe/Kyiv)
|
||||
**Last replay attempt**: 2026-05-24T05:07+03:00 (Europe/Kyiv) — replay re-checked
|
||||
**Last replay attempt**: 2026-05-26T13:06+03:00 (Europe/Kyiv) — replay re-checked
|
||||
at start of next `/autodev` invocation. PyPI re-queried via
|
||||
`python3 -m pip index versions gtsam`: only `gtsam 4.2` is published.
|
||||
Replay condition (numpy>=2 stable wheels) still NOT met. Leftover remains open.
|
||||
|
||||
@@ -0,0 +1,51 @@
|
||||
# Leftover: EVIDENCE_OUT default is a hardcoded container path
|
||||
|
||||
**Created**: 2026-05-26
|
||||
**Last replay attempt**: 2026-05-26
|
||||
**Category**: Test infrastructure defect (non-tracker leftover — code fix, not a deferred tracker write)
|
||||
**Surfaced by**: autodev cycle 3 Step 15 (Performance Test) — `_docs/06_metrics/perf_2026-05-26_cycle3-tier1-probe.md` "Findings worth tracking" item 3.
|
||||
|
||||
## Problem
|
||||
|
||||
`e2e/runner/conftest.py:56`:
|
||||
|
||||
```python
|
||||
default=os.environ.get("EVIDENCE_OUT", "/e2e-results/evidence")
|
||||
```
|
||||
|
||||
The default path `/e2e-results/evidence` is the container mount inside the Tier-1 Docker harness and the Tier-2 Jetson run script. On a developer Mac/Linux workstation invoking `python -m pytest e2e/tests/performance/` directly (no Docker, no Jetson), this hook fires in `nfr_recorder.pytest_sessionfinish` and tries to create the directory, failing with:
|
||||
|
||||
```
|
||||
OSError: [Errno 30] Read-only file system: '/e2e-results'
|
||||
```
|
||||
|
||||
(macOS — the volume `/` is read-only at the filesystem root.) On Linux hosts it would fail with `PermissionError` for the same reason — `/e2e-results` is not writable by a non-root user.
|
||||
|
||||
## Workaround (used today)
|
||||
|
||||
```bash
|
||||
EVIDENCE_OUT="$(pwd)/e2e-results/cycle3-tier1-probe/evidence" \
|
||||
python -m pytest e2e/tests/performance/ -v --tb=short
|
||||
```
|
||||
|
||||
This produced a clean exit-0 run with the expected 24 SKIPPED outcomes.
|
||||
|
||||
## Proposed fix
|
||||
|
||||
Change `e2e/runner/conftest.py:56` to default to a workspace-relative path when neither `--evidence-out` nor `EVIDENCE_OUT` is set. Two viable shapes:
|
||||
|
||||
1. **Workspace-relative default**: `default=os.environ.get("EVIDENCE_OUT", str(Path(__file__).resolve().parents[2] / "e2e-results" / "evidence"))`.
|
||||
2. **Lazy fallback inside the recorder**: leave the default unset; if `evidence_dir` is `None` at session finish, skip emission and warn — useful for `--collect-only` or smoke runs where evidence output is genuinely not needed.
|
||||
|
||||
Either shape preserves backward compatibility with the Docker / Jetson scripts (they pass `--evidence-out` explicitly).
|
||||
|
||||
## Why not fix in this cycle
|
||||
|
||||
Per `coderule.mdc` § Scope discipline: "Unrelated issues elsewhere: do not silently fix them as part of this task. Either note them to the user at end of turn and ASK before expanding scope, or record in `_docs/_process_leftovers/` for later handling." Cycle 3 was pre-flight / route-driven seeding work; the EVIDENCE_OUT default has no relationship to that scope. Recording here for either:
|
||||
|
||||
- Next cycle's New Task step to pick up as a small (~1 pt) housekeeping ticket, OR
|
||||
- A drive-by fix during the next test-infrastructure touch (e.g. when AZ-444 Tier-2 harness lands).
|
||||
|
||||
## Replay condition
|
||||
|
||||
This is a **code-fix leftover**, not a tracker-write leftover. There is nothing to "replay against the tracker". Resolution = land the conftest change above and verify a Tier-1 host run of `pytest e2e/tests/performance/` exits cleanly without `EVIDENCE_OUT` pre-set. Once that PR merges, delete this leftover.
|
||||
Reference in New Issue
Block a user