Conversation
|
Current status: made it to the end of phase 1 (launched jobs), but the MPAS-Analysis jobs didn't have sufficient wall times allocated. (Note: because of #764, it is usually better to rerun from scratch in this case). Action items:
|
f33b563 to
ed8e6fc
Compare
|
Using the latest commit (88cdcb2), I've made it to phase 2. It turns out I needed to update |
|
I've run through phase 3 now. There are a number of issues to resolve before fully switching from the manual testing workflow to this one. Immediate KeyError on later zppy runsI cannot get Phase 2 to work in an automated manner. I can launch Status file errorsI'm not sure how these could possibly be real failures (i.e., not caused by this branch), considering the last change to To be certain though, I will have to do the usual workflow and see if the same thing happens or not. MPAS Analysis errorscd /lcrc/group/e3sm/ac.forsyth2/zppy_weekly_comprehensive_v2_output/zppy_main_branch_test_20260126_run4/v2.LR.historical_0201/post/scripts
cat mpas_analysis_ts_1980-1984_climo_1980-1984.o1135588gives: OutputI had extended the time limit (here) because it was hitting the time limit, but it turns out the time limit isn't the problem at all. The job stays active even after the segmentation fault, but doesn't actually do anything to recover from it. Notes:
PCMDI Diags errorscd /lcrc/group/e3sm/ac.forsyth2/zppy_weekly_comprehensive_v3_output/zppy_main_branch_test_20260126_run4/v3.LR.historical_0051/post/scripts
cat pcmdi_diags_variability_modes_atm_model_vs_obs_1985-1994.o1135637gives: OutputRelevant lines, though I'm not sure why they aren't working:
Notes:
|
|
After running the standard manual weekly test, I've confirmed the That means this branch for automated testing has two major issues to resolve:
|
|
#803 has some helper functions that can at least partially automate the process until this more complete automation is merged. |
Summary
Objectives:
Issue resolution:
Select one: This pull request is...
Small Change