Python sys tests much longer with added tower testing...

[ekluzek]

#2406 makes the python system testing much longer. It's still less than an hour but a good fraction of it though. This is something that would help our python development and testing if we make it shorter. The reason for the length is really #2885. So fixing it should resolve this.

I'm also wondering about breaking up python system tests to another set of "long_sys" tests, that maybe we don't run as often? And actually if we ran that test list as part of aux_clm hour long testing would be fine.

[adrifoster]

@ekluzek I agree I think we should move the "building" part of this into our aux_clm testing and keep the python system tests quick.

[ekluzek]

@adrifoster but is it OK for us to bring them in as they are now? And fix it later? Or should we see if we can fix it now? I suppose if it takes too long, it might not be worth it, but it also could be easy to fix. What do you think?

[adrifoster]

@ekluzek my inclination is to yes bring this in now. we can have a separate PR to move long tests to aux_clm, and then this long testing will get fixed when #2885 is fixed?

[adrifoster]

@ekluzek to clarify - since this test shouldn't be long I would leave it here (even in that future PR I mentioned)

[ekluzek]

Perfect, that is what we will do.

[ekluzek]

Actually, it only changes the time from about 6 minutes to about 21 minutes, for all of the python sys tests. So better than I was initially thinking...

[wwieder]

@samsrabin has a fix for #2885 and he can pull out larger single point work to address this issue

[samsrabin]

In my testing of ctsm5.3.024, test_sys_run_tower.py takes about 871 seconds (n=2). PR #2963 speeds this up by >90% (~82 seconds, n=3). I will mark that PR as closing this issue.

[wwieder]

Thanks for doing this quickly, Sam.