-
Notifications
You must be signed in to change notification settings - Fork 388
Fix eighteen broken coastal test cases #662
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
Fix eighteen broken coastal test cases #662
Conversation
mark-petersen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have time to test, but if it works for you @xylar go ahead and merge with the green button when you are ready.
|
@sbrus89 could you approve? Visual inspection is probably fine here. |
I'm concerned that this attitude is becoming pervasive in COMPASS. As a result, tests are frequently broken like here and it makes them impossible to use as a baseline. As it is, I have to test several dozen test cases in #563 to make sure that work has not done any harm. Each broken test case adds considerable additional work to that process, including PRs like this one to fix them. As I have complained in the past, it becomes very difficult to maintain the COMPASS infrastructure if the test cases are not exercised on a regular basis and that job cannot fall exclusively to me. |
This one irks me especially. I do not have time to fix these tests (they are not mine!) but I took the time anyway and I will take the time to test them each twice more than I would have had to if they worked. |
efe9d26 to
4a1cfb1
Compare
TestingTests that now run successfully:
|
4a1cfb1 to
66408f3
Compare
|
@sbrus89, while there are 2 tests of mine still running, I think this is ready for you to review. My preference would be for you to set up and re-run these tests yourself and make sure you also see them working. If that's not possible, let's chat about how to review these fixes meaningfully with more than just a glance at the code changes. |
|
@xylar, thanks very much for your help maintaining these. I will take a look. Can we possibly do this PR into |
I think these issues should have been dealt with in #485. I am not happy that I didn't get a chance to do this level of testing before approving that PR and I will not make that mistake again. Since we are considering |
|
FYI, my testing is in: |
|
The |
|
This one is fine to merge before |
sbrus89
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…3800) Update mpas-source: compass only This PR brings in a new mpas-source submodule with changes only to the ocean core. All of the changes are to the COMPASS testing code that is not used in E3SM, so this PR should have no effect on E3SM. The COMPASS commits are: * MPAS-Dev/MPAS-Model#563 'xylar/ocean/remove_jigsaw_to_mpas' * MPAS-Dev/MPAS-Model#662 'xylar/ocean/fix_broken_compass_tests' * MPAS-Dev/MPAS-Model#664 'xylar/ocean/fix_plot_initial_state' [BFB]
Update mpas-source: compass only This PR brings in a new mpas-source submodule with changes only to the ocean core. All of the changes are to the COMPASS testing code that is not used in E3SM, so this PR should have no effect on E3SM. The COMPASS commits are: * MPAS-Dev/MPAS-Model#563 'xylar/ocean/remove_jigsaw_to_mpas' * MPAS-Dev/MPAS-Model#662 'xylar/ocean/fix_broken_compass_tests' * MPAS-Dev/MPAS-Model#664 'xylar/ocean/fix_plot_initial_state' [BFB]
…an/develop Fix eighteen broken coastal test cases MPAS-Dev#662 This merge removes the e3sm_coupling step from the coastal/Maine test case. It is not configured properly and is not needed. It also fixes links to cull_mesh.py in two USDEQU120cr10rr2 tests.
This merge removes the
e3sm_couplingstep from thecoastal/Mainetest case. It is not configured properly and is not needed.It also fixes links to
cull_mesh.pyin twoUSDEQU120cr10rr2tests.