Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Phase out of Izumi for our testing #2622

Open
ekluzek opened this issue Jun 26, 2024 · 1 comment
Open

Phase out of Izumi for our testing #2622

ekluzek opened this issue Jun 26, 2024 · 1 comment
Labels
testing additions or changes to tests

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented Jun 26, 2024

Izumi has been a great test platform for us that provides several benefits:

  1. The Nag compiler which catches issues other compilers haven't (made it easier to find problems)
  2. Machine available when NCAR HPC is not
  3. Easy to run quickly without waiting in the batch queue
  4. Different compiler versions than NCAR HPC which can helps us to identify problems with compiler versions
  5. Same as above but doubles our compiler version testing environment
  6. Helps us ensure inputdata are rimported
  7. Similar environment to University users

However, we are running into these problems:

  • Hardware is beyond it's expected life
  • Not well supported by NRIT, with only one admin with experience on it
  • NRIT wants us to move away from having a supported cluster in CGD
  • We are having environment problems where it works for some, but not all of us

As such we need to have a plan to move our testing away from Izumi. We need to look at this as a group and decide what that will look like. Some tests might need to be moved to Derecho. Possibly we can change warnings to errors on other compilers (as being done in CMEPS/CDEPS) on NCAR HPC. Possibly we can get access to another machine to serve the purpose that Izumi does.

This came up at today's CSEG meeting and was discussed there.

@briandobbins

@ekluzek ekluzek added testing additions or changes to tests next this should get some attention in the next week or two. Normally each Thursday SE meeting. labels Jun 26, 2024
@ekluzek
Copy link
Collaborator Author

ekluzek commented Jun 26, 2024

Tasks that come to mind for me:

  • Run the izumi test list on Derecho and just see what it does
  • Examine test list to see if there are tests only done on izumi (make sure they have a copy on Derecho)
  • Add a test list for Casper to help replace izumi (but see Single Site Test Attempt on Casper (fails) #2293) (would have to only be single point sites)
  • Move Derecho single point sites for testing to Casper
  • Examine what CMEPS/CDEPS does for warnings and replicate it for CTSM
  • Figure out a protocol for ensuring inputfiles added to XML get rimported

Longer term:

  • Ask CISL to add a NAG license to Derecho (move Izumi nag tests to that)
  • Look into options for another machine to fill this role
  • Get the team access to that machine
  • Move the Izumi test list over to that machine

@ekluzek ekluzek removed the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Jul 8, 2024
@ekluzek ekluzek added this to the ctsm6.0.0 (code freeze) milestone Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
testing additions or changes to tests
Projects
None yet
Development

No branches or pull requests

1 participant