-
Notifications
You must be signed in to change notification settings - Fork 214
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
New allow_error field for module system #2317
Conversation
This is necessary since implementations of environment modules are highly variable and some systems produce stderr output even when things are working fine. Default this to false since we want to catch errors on standard systems.
I guess I'm doing something wrong here. I've added allow_error to my config_machines.xml in the following way: Setting up a case using I noted that the error message references XSD file Any ideas? |
Yes, we need to add this field to the schema definition. The problem would have been detected earlier had full testing been done on this PR prior to merging. |
Fixed in #2654 |
Thanks Jim |
@jedwards4b , does E3SM not do XSD checking on this file? We've had allow_error on for months. |
Its probably version 1 vs version 2 behavior. |
It seems like if you created a case on melvin, summit or summitdev it would have an error. The test is on env_mach_specific.xml rather than on the config_machines.xml file. |
@jedwards4b , you'd think so, but i've created 10's of thousands of cases on melvin since this was introduced. |
I think @rljacob may be right and it's the version , but then I don't understand why @lvankampenhout ran into the problem - is he using cesm or e3sm? |
@jedwards4b he may be the first CESM person to try to use it. |
ah - that makes sense then. |
yes I'm using CESM |
Fix format statement preventing write of coupler aux history files. [BFB]
This is necessary since implementations of environment modules are
highly variable and some systems produce stderr output even when
things are working fine.
Default this to false since we want to catch errors on standard
systems.
Test suite: code-checker, by-hand
Test baseline:
Test namelist changes:
Test status: bit for bit
Fixes #1625
User interface changes?: Y, new allow_error attribute for module systems
Update gh-pages html (Y/N)?: N
Code review: @jedwards4b