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

CIME does not always download all the necessary input files for test cases that modify case2 #4400

Closed
jgfouca opened this issue Apr 19, 2023 · 6 comments · Fixed by #4481
Closed

Comments

@jgfouca
Copy link
Contributor

jgfouca commented Apr 19, 2023

We are seeing that some test cases will sometimes need different input files for their case2 (ERP, PEM). These files don't appear to be automatically downloaded by CIME which can lead to failures.

@jgfouca
Copy link
Contributor Author

jgfouca commented Apr 19, 2023

@jonbob , does this summarize the issue correctly?

@jedwards4b
Copy link
Contributor

I wonder if the issue is due to case2 being submitted from a (compute) node that doesn't have internet access? One way to solve this might be to explicitly call check_inputdata --download from the ERP and PEM tests in the case2 directory.

@jonbob
Copy link
Contributor

jonbob commented Apr 19, 2023

That might do it -- it's only the mpas graph (decomposition) files that are different and get missed. And thanks @jgfouca, I think that covers it. The graph files should be listed in the mpas input_data_list's, so hopefully it's as simple as calling check_download from case2

@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 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 May 20, 2023
@jgfouca jgfouca removed the Stale label May 22, 2023
@jonbob
Copy link
Contributor

jonbob commented May 22, 2023

This issue is still important to E3SM

@github-actions
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants