Should the CI fail again when the NEST build raises warnings?

[nicolossus]

Before the merge of #2590 with the new CI setup, the CI would fail if any warnings were raised in the building of NEST. Known warnings could be excluded in the now removed parse_build_log.py.

Currently, the CI passes even though warnings are raised. Do we want this new behavior or should the old behavior be reinstated?

[nicolossus]

@heplesser @jougs @terhorstd Any opinions?

[jougs]

Generally, I think we should strive for zero warnings during the build.

Can you have a look at how to get the old behavior back? I assume this is not so easy now that we don't write the logs to our own files anymore, or is there a way to programmatically look at the output that GitHub Actions caches?

[github-actions]

Issue automatically marked stale!

[github-actions]

Issue automatically marked stale!