Catch warnings in CI pipeline
As it turned out in #306 (closed) the CI pipeline will run fine without errors even though the tests produce any amount of warnings. New warnings should get the attention of developers.
Question: How strict are we?
- No warnings allowed at all
- limit number of allowed warnings, e.g. to number of known warnings
- label or match known warnings and notify about new/unknown warnings
Problem A: detection of warnings
- https://metacpan.org/pod/Test::NoWarnings can make all warnings fatal
Problem B: notification
- make pipeline fail
- some kind of soft fail
- GitLab CI has
allow_failure
to proceed pipeline but indicate problems - allow certain exit codes https://stackoverflow.com/questions/52167571/how-to-cause-a-job-to-finish-with-warning-in-gitlab
- log test output to file, check file for warnings in additional job https://stackoverflow.com/questions/59680450/how-to-detect-compiler-warnings-in-gitlab-ci
- GitLab CI has