Apparently some systems are still configured to use GMT instead of
UTC after all. This included our own GitHub CI runner config.
Oops. This made the previous commit fail to pass the CI test run.
We can't win this one, it's got to be either one or the other.
UTC is the international standard on which civil time is based.
GMT is often taken as synonymous for UTC, but in navigation,
it can differ from UTC by up to 0.9 seconds. Ref.:
https://en.wikipedia.org/w/index.php?title=Greenwich_Mean_Time&oldid=963422787
The more ambiguous term should not be the first preference.
src/cmd/ksh93/tests/builtins.sh:
- Before checking 'printf %T now' output against 'date' output,
change any ' GMT ' in the latter to ' UTC '.
.github/workflows/ci.yml:
- Set time zone to UTC, not GMT.
.github/workflows/ci.yml:
- Disable Mac build as the GitHub runners appear to be broken
(e.g. SIGCHLD fails, unlike on real Macs) and tend to hang.
- For the Linux build:
- Set GMT timezone for 'printf %T' tests in builtins.sh.
- Set the ulimit for open files to 1024 as the subshell.sh tests
need a lot of open files.
- As the runners lack the POSIX standard /dev/tty device, use the
script command to provide a fake /dev/tty for the bracket.sh
tests that use 'test -t $fd'.
Ref.: https://github.com/actions/runner/issues/241
