Raymond Toy pushed to branch issue-453-update-make-options-for-analyzer at cmucl / cmucl Commits: c937739e by Raymond Toy at 2025-11-09T16:21:59-08:00 Always save analyzer artifacts Instead of using the exit code (as done previously), modify the artifacts rule to include "when: always". This is simpler and more obvious about what we want. - - - - - 1 changed file: - .gitlab-ci.yml Changes: ===================================== .gitlab-ci.yml ===================================== @@ -301,6 +301,7 @@ linux:static-analyzer: tags: - linux artifacts: + when: always paths: - analyzer.log needs: @@ -312,15 +313,7 @@ linux:static-analyzer: # console. If someday there's less or no output, we can consider # having the logs go to the console too. - make -C build-4/lisp clean - # From - # https://docs.gitlab.com/ci/yaml/script/#ignore-non-zero-exit-codes - # - # If the analyzer fails, we still want the logs to be saved. So - # ignore the failure, but also print a message so we know - # something happened. - - exit_code=0 - - make -C build-4/lisp ANALYZER=-fanalyzer > analyzer.log 2>&1 || exit_code=$? - - if [ $exit_code -ne 0 ]; then echo "Analyzer failed with code $exit_code"; fi; + - make -C build-4/lisp ANALYZER=-fanalyzer > analyzer.log 2>&1 #### OpenSUSE jobs #### opensuse:install: View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/c937739e1c717d99cfcfcea3... -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/-/commit/c937739e1c717d99cfcfcea3... You're receiving this email because of your account on gitlab.common-lisp.net.