Skip to content

Make sure failures in multiline CI steps are not swallowed. #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

dabrahams
Copy link
Contributor

@dabrahams dabrahams commented Nov 9, 2023

Description

Cause failures in CI to be reported

Checklist

Ensure that your pull request has followed all the steps below:

  • Code compilation.
  • All tests passing.
  • No new SwiftLint issues.
  • Added new unit tests, if applicable.
  • Extended the documentation (including README), if applicable.
  • Updated version in CBORCoding.podspec following semver guidelines.
  • Ran workflowtests.sh and passed.
  • Added myself to the CONTRIBUTORS file.

Proposed changes

Without this change, it is possible to have a passing CI job even though the build failed, e.g.

https://github.com/dabrahams/CBORCoding/actions/runs/6806944368/job/18509010389#step:4:99

And in fact you will see that this PR reveals 1 linting problem and 11 test failures on ubuntu-latest that were being ignored.

@dabrahams dabrahams mentioned this pull request Nov 9, 2023
8 tasks
@SomeRandomiOSDev SomeRandomiOSDev merged commit e12b478 into SomeRandomiOSDev:main Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants