Standalone gadi (#2)#947
Conversation
|
I can't see if/how I made this fail in the CI tests: |
|
I think github actions changed again and it's broken. UGH!!! See also https://github.com/apcraig/CICE/actions/runs/8912669968/job/24476572429 which is just running the current CICE main (but off my fork). Will try to do some debugging. |
|
Please merge/rebase from the current main head. GHActions should be working again. |
| setenv ICE_MACHINE_MACHNAME gadi | ||
| setenv ICE_MACHINE_MACHINFO "Intel Xeon Scalable" | ||
| setenv ICE_MACHINE_ENVNAME intel | ||
| # setenv ICE_MACHINE_ENVINFO ${module list} |
There was a problem hiding this comment.
I think you might also have an error here. It's possible the failure you were getting was unrelated to the overall problem. If you continue to have problems, my guess is that it's because these env variables probably have to be defined. Try changing to
setenv ICE_MACHINE_ENVINFO unknown
(or similar) and see if that fixes the problem.
|
Github Actions is working again. But this PR now shows the changes associated with the merge. I think we prefer not to see those. Did you rebase? Any chance you could fix that? Another option is to create a new branch off Consortium main, merge this branches changes onto the new branch, and create a new PR. Let me know if that makes sense. Maybe you have a more clever way to handle this. |
|
Thanks Tony - yes operator error. Ill fix |
* Standalone gadi setup (#1)
|
It looks like we might have an intermittent bug in the CI: https://github.com/ACCESS-NRI/CICE/actions/runs/8916589708 passed and https://github.com/CICE-Consortium/CICE/actions/runs/8916589961/job/24488267484 failed on the same commit ! Anyway, I made the change suggested and it passed this time (but I can't see how its related). Don't merge yet, ill have a go tomorrow at setting a more meaningful value for ICE_MACHINE_ENVINFO |
|
This should be ready to merge @apcraig :) |
This is the setup for doing standalone builds on the ACCESS computers. This affects build set-up only, not CICE code.
For detailed information about submitting Pull Requests (PRs) to the CICE-Consortium,
please refer to: https://github.com/CICE-Consortium/About-Us/wiki/Resource-Index#information-for-developers
PR checklist
Add config for using cice standalone build scripts on Gadi / for ACCESS development
@anton-seaice
@apcraig
ENTER INFORMATION HERE
Add standalone build config for gadi supercomputer