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

regression test test_d_create_clone_new_user FAILS #4630

Closed
jedwards4b opened this issue May 14, 2024 · 4 comments
Closed

regression test test_d_create_clone_new_user FAILS #4630

jedwards4b opened this issue May 14, 2024 · 4 comments
Assignees

Comments

@jedwards4b
Copy link
Contributor

@jasonb5 this looks like it's due to #4609

======================================================================
FAIL: test_d_create_clone_new_user (test_sys_create_newcase.TestCreateNewcase)

Traceback (most recent call last):
File "/home/runner/work/CMEPS/CMEPS/cesm/cime/CIME/tests/test_sys_create_newcase.py", line 264, in test_d_create_clone_new_user
self.run_cmd_assert_result(
File "/home/runner/work/CMEPS/CMEPS/cesm/cime/CIME/tests/base.py", line 141, in run_cmd_assert_result
self.assertEqual(stat, expected_stat, msg=msg)
AssertionError: 1 != 0 :
COMMAND: ./xmlchange CIME_OUTPUT_ROOT=/home/this_is_not_a_user/cesm/scratch/scripts_regression_test.20240514_194710/TestCreateNewcase
FROM_DIR: /home/runner/cesm/scratch/scripts_regression_test.20240514_194710/TestCreateNewcase/testcreatenewcase
SHOULD HAVE WORKED, INSTEAD GOT STAT 1
OUTPUT:
ERRPUT: Detected diff in locked file 'env_build.xml'
'CIME_OUTPUT_ROOT' has changed from '/home/runner/cesm/scratch/scripts_regression_test.20240514_194710/TestCreateNewcase' to '/home/this_is_not_a_user/cesm/scratch/scripts_regression_test.20240514_194710/TestCreateNewcase'
ERROR: For your changes to take effect, run:
./case.build --clean-all
./case.build

@jasonb5
Copy link
Collaborator

jasonb5 commented May 14, 2024

@jedwards4b Will have this fixed shortly.

@jasonb5
Copy link
Collaborator

jasonb5 commented Jun 14, 2024

@jedwards4b Was this fixed by #4631?

Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days.

@github-actions github-actions bot added the Stale label Sep 13, 2024
Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants