Set up automated tests via Github Actions

[timlichtenberg]

Optimally, all newly introduced modules and functions should be automatically tested with every pull request. We will start to continuously work these in, also for older parts of the code that are not being tested as of yet.

See https://docs.github.com/en/actions.

Connected to: FormingWorlds/PROTEUS#71, FormingWorlds/PROTEUS#83

[timlichtenberg]

First test for JANUS: FormingWorlds/JANUS#21

[timlichtenberg]

To be updated list of automated tests that need to be included:

• [x] JANUS: Pure steam thermal limit recovery (demo_runaway_greenhouse.py)
• [x] JANUS: Compile and build SOCRATES
• [ ] MORS: Check stellar flux consistency between SOCRATES downward fluxes and MORS output
• [ ] PROTEUS: Whole PROTEUS run until solidification with baseline configuration

[nichollsh]

For the model to be tested, there will also need to be a pipeline for configuration it via the GitHub actions framework. This might mean an action for compiling SOCRATES, and another for configuring conda (for example). These aren't physical tests, and aren't as useful, but will also need to be done.

[timlichtenberg]

This sounds good to me, we should do this anyway to ensure that SOCRATES can indeed by meaningfully compiled and conda configured. Any tips on that @lsoucasse and @stefsmeets?

[nichollsh]

On this topic, I've tried to streamline SOCRATES compilation in AGNI which requires only running two scripts. We could copy this exactly in JANUS.

[lsoucasse]

We now have GH actions for Janus, Socrates and Agni. Tests of the PROTEUS framework will be setup at a later stage so I move this issue to TBD.

[stefsmeets]

Is there any basic example script that we could reuse for this? At least as a start.