Restore correct conda activate message for Cheyenne#424
Conversation
Restore correct `conda activate` message for Cheyenne
|
Machine: jet |
|
Machine: hera |
|
@MichaelLueken Do you know the status of these automated tests? It shows up as "errored" here on github, but checking on disk on Cheyenne it looks like the tests succeeded: /glade/scratch/epicufsrt/jenkins/workspace/fs-srweather-app_pipeline_PR-424__2/ This change is documentation only so it shouldn't result in any failures. |
|
Visual inspection of the Jenkins CI test results show that all tests on Cheyenne (both Intel and GNU) successfully passed. The tests also successfully passed on Orion, Gaea, and Jet. The tests have stalled out on Hera, but the tests that have been submitted and run have all passed successfully. Merging this work now. |
|
@mkavulich It looks like the agents were disconnected for Hera, Orion, and Cheyenne, which ultimately broke the Jenkins automated testing. The experiment directories were checked and all tests had successfully passed on Cheyenne (both Intel and GNU), Orion, Jet, and Gaea. Hera was hanging, but the tests that had been submitted and run successfully completed. Plus, as you noted, this is more of a documentation change (making sure the whole path to the regional_workflow conda environment is specified after loading wflow_cheyenne). So, I have gone ahead and merged your changes. |
DESCRIPTION OF CHANGES:
PR #413 inadvertently modified the
conda activatemessage printed to screen for Cheyenne. Unlike NOAA RDHPC platforms, Cheyenne requires the full path to the conda environment to activate properly.Type of change
TESTS CONDUCTED:
This is a print-only change, but have kicked off automated tests on Hera and Jet out of an abundance of caution.
DEPENDENCIES:
None
DOCUMENTATION:
Self-documenting
ISSUE:
None
CHECKLIST