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
This issue is reproducible on both anlworkstation and summit.
It is caused by PR #3449: Improve case.setup clean (happens for --clean or --reset)
Steps to reproduce:
git clone https://github.com/ESMCI/cime.git
cd cime/scripts
./create_test DAE.ww3a.ADWAV --no-run
Errors are:
...
WARNING: Test case setup failed. Case2 has been removed, but the main case may be in an inconsistent state. If you want to rerun this test, you should create a new test rather than trying to rerun this one.
ERROR: Cannot move past core phase 'SETUP', it didn't pass:
CaseStatus shows:
case.setup error
ERROR: FakeCase does not support getting value of 'SMP_PRESENT'
Another way to reproduce this issue:
git clone https://github.com/ESMCI/cime.git
cd cime/scripts
./create_test DAE.ww3a.ADWAV --no-build
cd to Case dir
./case.setup --reset
Output messages:
Successfully cleaned .case.test
Successfully cleaned env_mach_specific.xml
Successfully cleaned Macros.make
Successfully cleaned Macros.cmake
ERROR: FakeCase does not support getting value of 'SMP_PRESENT'
The text was updated successfully, but these errors were encountered:
case.setup: Fix case reset on some machines
Removing env_mach_specific.xml triggered the FakeCase path in
BuildConf.configure. This path doesn't work if the machine is using
advanced attribute selectors (e.g. SMP_PRESENT) in their environment
block in config_machines.xml.
case_setup only needs BuildConf.configure to recreate the env_mach_specific.xml
file and the Macro files.
Test suite: scripts_regression_tests
Test baseline:
Test namelist changes:
Test status: bit for bit
Fixes#3473
User interface changes?:
Update gh-pages html (Y/N)?:
Code review: @jedwards4b
This issue is reproducible on both anlworkstation and summit.
It is caused by PR #3449: Improve case.setup clean (happens for --clean or --reset)
Steps to reproduce:
Errors are:
CaseStatus shows:
Another way to reproduce this issue:
Output messages:
The text was updated successfully, but these errors were encountered: