diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-19 13:20:05 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-19 13:20:05 -0500 |
| commit | 574ca0d4427256788574ff6380fec382f91ceb4a (patch) | |
| tree | 479d200070d7c3bc4e5d4e3390f7d772290c4a37 /scripts/testing/setup-testing-env.sh | |
| parent | f6ea3a1bd9767324fea36ddc89ef18a0a780c43c (diff) | |
| download | archsetup-574ca0d4427256788574ff6380fec382f91ceb4a.tar.gz archsetup-574ca0d4427256788574ff6380fec382f91ceb4a.zip | |
chore: log AUR exit-0 fix verification and close the sub-task
Two updates in todo.org. I marked the two dconf entries in the `[#B] Fix install errors` parent body as RESOLVED in `762caef`, since the system-wide dconf db migration verified clean in last night's VM run.
I converted the `*** TODO [#B] AUR exit-0 logged as error` sub-task into a dated event-log entry. The root cause was a bash if-compound semantics trap in `retry_install` (the if-compound exits 0 when no condition tested true, overwriting the eval's actual exit code that `last_exit_code=$?` was trying to capture). Today's VM run verified the fix: `mkinitcpio-firmware` and `tidaler` now report `error code: 1` instead of the misleading `error code: 0`.
Diffstat (limited to 'scripts/testing/setup-testing-env.sh')
0 files changed, 0 insertions, 0 deletions
