Catch unexpected errors in Bourne shell scripts.

[tee3]

Check the exit status of commands directly in Bourne shell script.

Proposed changes

This ensures that errors in the script will be caught during continuous integration.

Types of changes

Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Documentation content changes
• Other (please describe):

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I searched the discussions
• I searched the closed and open issues
• I read the contribution guidelines
• I added myself to the copyright attributions for significant changes
• I checked that tests pass locally with my changes
• I added tests that prove my fix is effective or that my feature works
• I added necessary documentation (if appropriate)

Further comments

N/A

[tee3]

I guess this runs differently in continuous integration. I'll take a look and try to get it going.

[grafikrobot]

Closing this as it's been a while. If you ever get back this, re-open it.