Hui Zhou

The time-out is set by Jenkins,and the test script is killed by Jenkins, thus, there is nothing the test script can do once it is killed. Whatever the solution should...

I see. Could you try add an additional Jenkins job step with following shell code -- ``` if ! grep '' test/mpi/summary.junit.xml ; then echo '' >> test/mpi/summary.junit.xml fi ```...

I see. Maybe try -- ``` if ! grep '' test/mpi/summary.junit.xml ; then mv test/mpi/summary.junit.xml incomplete.xml echo '' > test/mpi/summary.junit.xml cat incomplete.xml >> test/mpi/summary.junit.xml echo '' >> test/mpi/summary.junit.xml fi ```...

> Would it be possible to make these changes? Sure. I can make a PR with these changes. You are also welcome to contribute the PR yourself. For new authors,...

On a second thought, maybe it is possible for `runtests` to trap the kill signal and wrap XML report. I'll give it a try later.

@tonyzinger Could you try https://github.com/pmodels/mpich/pull/6111?

I tested using Jenkins' "Run with timeout" job step, and the console log are - ``` ... Build timed out (after 45 minutes). Marking the build as failed. Build was...

If the script can't catch the signal (e.g. SIGKILL), then there is nothing the script can do. Currently -- https://github.com/pmodels/mpich/blob/108b611d6fdef3f6268be42e93f4b0320f96a6d5/test/mpi/runtests#L1133-L1135 If you can find out which signal Jenkins' used to...

I don't have much clue, but could you try the step without `try-catch`?

> One other suggestion, when you print out the the testcase test number in the junit format, could you make this a 5 digit number with leading zeros. Sure. I'll...