Repository navigation
Commit f269e63
committed
test(e2e): fail where the baseline capture fails, not where it is read
The seed side carried the same fail-open the platform verify just lost:
`kubectl get pods -A | awk ... > file || true` takes the exit status of
the pipeline's LAST command, and the `|| true` discarded even that. A
failed listing therefore wrote an EMPTY baseline and passed.
An empty baseline is not silent — verify/platform reads every
currently-unbound PV as newly unbound — but it fails forty minutes later,
in the wrong suite, naming resources that were unbound before the upgrade
ever started. Take both listings out of their pipelines so `set -e` sees
them, and drop the `2>/dev/null` that was hiding the reason.
The two intermediates go to /tmp rather than the baseline directory, so
what the verify phase reads there is still exactly the two snapshots this
suite documents.
Assisted-By: Claude <[email protected]>
Signed-off-by: Myasnikov Daniil <[email protected]>1 parent fe40b2b commit f269e63
1 file changed
Lines changed: 10 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
24 | 24 | | |
25 | 25 | | |
26 | 26 | | |
27 | | - | |
28 | | - | |
29 | | - | |
30 | | - | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
31 | 37 | | |
32 | 38 | | |
33 | 39 | | |
| |||
0 commit comments