The previous commit broadened the plan and resolve_assets label gates to admit
upgrade-e2e, but hack/promote-gate-contract.bats pins those two expressions as
exact grep -cF literals. Both counts fell to zero, bats-unit-tests failed, and
because "Unit & controller tests" gates finalize, the required E2E Tests check
and this PR's own upgrade lane were both skipped — the commit meant to make the
label start a run stopped every run instead.
I broke this by running the unit suite before writing that commit rather than
after; pre-commit does not cover bats-unit-tests, so it went unnoticed.
Update both assertions to the broadened expressions, and add a case pinning the
label end to end: admitted by the `labeled` allow-list in both plan and
resolve_assets, honoured by the job's own condition, and named "Upgrade E2E
Test" so it cannot collide with the required "E2E Tests" context and stop being
advisory. Note the label is double-quoted inside the JSON allow-list — matching
the single-quoted form counts zero and asserts nothing.
Verified non-vacuous: narrowing the plan gate back to the full-e2e-only literal
turns exactly one test red.
Also correct the MariaDB seed header, which still prescribed the 127.0.0.1
connection that commit f598c253 replaced — the same file documents that path as
OOM-killing the nano server container.
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
Myasnikov Daniil
2bd363ccbe