You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Latest commits related to the containerization broke the GLOBIOM-G4M script throughout the different stages (GLOBIOM ex-post reporting, G4M) as the output gdx are labelled now differently and seem to have been put also in different folders.
@acjbrouwer does it make sense to set-up automated testing of the link as you did for GLOBIOM or rather stick with local testing?
The text was updated successfully, but these errors were encountered:
Automated testing is a good thing but would take a lot of effort to set up on the Jenkins test server (an HT Condor installation and other environment updates would be required). Moreover, we're going to structurally revise things for the containerization, and having to update complex automated testing while doing so is an additional burden.
Post containerization, setting up automated testing should be rather easier. Now things are still very fragile.
Latest commits related to the containerization broke the GLOBIOM-G4M script throughout the different stages (GLOBIOM ex-post reporting, G4M) as the output gdx are labelled now differently and seem to have been put also in different folders.
@acjbrouwer does it make sense to set-up automated testing of the link as you did for GLOBIOM or rather stick with local testing?
The text was updated successfully, but these errors were encountered: