You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make the bash 3.2 array rule mechanical instead of remembered
This has now bitten twice in the same file: fixed once in "Expand
possibly-empty arrays the way macOS's bash 3.2 tolerates", reintroduced
with the Rosetta launcher, and both times it cost a full macOS build
that finished, validated, and then staged nothing.
Deciding case by case which array can be empty is the judgement that
failed, so the remaining expansions in the scripts that run on a
published host all take the tolerant form -- it means the same thing as
the plain one whenever the array has elements -- and a test refuses any
that do not. Against the parent of this branch it names lines 161 to 165
of build-host.sh, the ones that broke the nightly.
The test is static because it has to be: BASH_COMPAT=32 does not restore
the 3.2 behaviour, so nothing running on a Linux runner can reproduce it
by executing anything.
0 commit comments