diff options
| author | Thomas Schwinge <thomas@codesourcery.com> | 2022-03-22 10:29:21 +0100 |
|---|---|---|
| committer | Thomas Schwinge <thomas@codesourcery.com> | 2022-03-22 12:17:23 +0100 |
| commit | 10ff5d5507fea8e76837aab81dc6932fd6f8a3ea (patch) | |
| tree | 59f25b33c71b6cd636a6b44f62f57fa6dc5532f3 /gcc | |
| parent | 246fb48cbbb3dd6ad3a723cb9a9ead50a1d67103 (diff) | |
| download | gcc-10ff5d5507fea8e76837aab81dc6932fd6f8a3ea.zip gcc-10ff5d5507fea8e76837aab81dc6932fd6f8a3ea.tar.gz gcc-10ff5d5507fea8e76837aab81dc6932fd6f8a3ea.tar.bz2 | |
Merge 'Build logs' into 'Build' in '.github/workflows/ccpp.yml:jobs.build-and-check'
This avoids the supposed issue that in case that 'make' fails, the whole
'jobs.build-and-check' stops, and 'Build logs' isn't executed, and thus there's
no indication in the GitHub UI why 'make' failed.
Using a shell pipeline is OK; the exit code of 'make' isn't lost, as per
<https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsshell>,
'bash' is being run with '-o pipefail'.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions