Closed MTLehner closed 2 years ago
@SchroederB @pultar any ideas/comments?
There seem to many of these errors
Have we considered using the logging
package? There we could have a global state of verbosity. However, I actually don't like turning off warnings - maybe it's better to address them. For example, we could debate having an Azure pipeline that has a local version of gromos installed. That should be compliant with gromos license while at the same time enabling better tests.
Or we use service containers for GitHub actions: https://docs.github.com/en/actions/using-containerized-services/about-service-containers
CI Warnings
Problem
Currently many test throw a huge number of Warnings: Leading to >60000 Warnings. Nobody reads all these warnings. Even though some might be useful information.
Possible solution
We could try to reduce the number of stupid warnings. Many come from the submission system and files not existing in the GitHub CI (for example GROMOS). My suggestion is to rework the test so that no more unimportant Warnings are thrown.
One tool would be too decrease the verbose level and turn of some verbosity completely. An other one would be to make the warnings smart.
Ides?
I'm open for other ideas of how to tackle this problem