mateo-berri a9e918577b ci(e2e): run the access_control canary on harness changes and name failed tests ... A harness-only change (proxy_client.py, conftest.py, pytest.ini, the gateway config, .github/e2e-stack, or the workflow) selected nothing, so the stack was never exercised by the change that touched it. select_tests.py keeps the changed-file rule and adds the access_control suite whenever a harness file changes. The run step now reports the pytest exit code before the evidence check, prints pytest's summary line per pass so the rerun count is visible, and assert_tests_ran.py names each failed or errored test as classname::name		2026-09-05 18:46:51 -07:00
..
assert_tests_ran.py	ci(e2e): run the access_control canary on harness changes and name failed tests	2026-09-05 18:46:51 -07:00
down.sh	ci(e2e): run a PR's changed e2e tests three times behind a human-approved environment	2026-09-02 14:53:40 -07:00
secrets_to_env.py	fix(ci): mask only credential-length values in the e2e-changed log	2026-09-05 16:33:15 -07:00
select_tests.py	ci(e2e): run the access_control canary on harness changes and name failed tests	2026-09-05 18:46:51 -07:00
up.sh	fix(e2e): wait for every gateway before using a new model and keep the network rerun	2026-09-05 16:10:40 -07:00