Test CI shell configuration

[findepi]

No description provided.

[findepi]

per https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference it seems the run workflow steps are run with bad (bash's default) configuration, i.e. lacking set -euo pipefail

since we use multi-command run steps like

run: |
          export MAVEN_OPTS="${MAVEN_INSTALL_OPTS}"
          $MAVEN validate ${MAVEN_FAST_INSTALL} -pl '!:trino-docs,!:trino-server-rpm'
          # GIB doesn't run on master, so make sure the file always exist
          touch gib-impacted.log
          testing/trino-plugin-reader/target/trino-plugin-reader-*-executable.jar -i gib-impacted.log -p core/trino-server/target/trino-server-*-hardlinks/plugin > impacted-features.log
          echo "Impacted plugin features:"
          cat impacted-features.log

this would lead to masking errors.

currently, the PR only verifies documentation vs life

cc @nineinchnick @hashhar

[findepi]

@nineinchnick

the test returned

+ printf '%s\n' ehxB
+ false
ehxB
Error: Process completed with exit code 1.

-- the set -e is enabled, which is good and most important
but set -u is not enabled, which is not good.
i would also want set -o pipefail to be enabled too

what do you think?

[nineinchnick]

@nineinchnick

the test returned

+ printf '%s\n' ehxB
+ false
ehxB
Error: Process completed with exit code 1.

-- the set -e is enabled, which is good and most important but set -u is not enabled, which is not good. i would also want set -o pipefail to be enabled too

what do you think?

Let's try adding these: #13291