mpi-smp autobuild doesn't complete successfully

[nitbhat]

http://charm.cs.illinois.edu/autobuild/old.2020_10_22__01_06/mpi-linux-x86_64-smp.txt

[matthiasdiener]

Note that the test just before the hanging one already takes a very long time to finish:

../../../bin/testrun  ./pgm +p4 ++ppn 2 

Running on 2 processors:  ./pgm +ppn 2 
charmrun>  /usr/bin/setarch x86_64 -R  mpirun -np 2  ./pgm +ppn 2 
Charm++> Running on MPI version: 3.1
Charm++> level of thread support used: -1 (desired: 0)
Charm++> Running in SMP mode: 2 processes, 2 worker threads (PEs) + 1 comm threads per process, 4 PEs total
Charm++> The comm. thread both sends and receives messages
Converse/Charm++ Commit ID: fa8f13a
Charm++ built with internal error checking enabled.
Do not use for performance benchmarking (build without --enable-error-checking to do so).
Isomalloc> Synchronized global address space.
Charm++> Running on 1 hosts (1 sockets x 4 cores x 2 PUs = 8-way SMP)
Charm++> cpu topology info is gathered in 1.809 seconds.
test 0: initiated [blkinhand]
test 0: completed (5.99 sec)
test 1: initiated [posixth]
test 1: completed (0.05 sec)
test 2: initiated [future]
test 2: completed (0.69 sec)
test 3: initiated [bigmsg]
test 3: completed (1.14 sec)
test 4: initiated [vecsend]
test 4: completed (0.83 sec)
test 5: initiated [nodenum]
test 5: completed (2.15 sec)
test 6: initiated [specmsg]
test 6: completed (1.30 sec)
test 7: initiated [vars]
test 7: completed (2.27 sec)
test 8: initiated [priotest]
test 8: completed (0.52 sec)
test 9: initiated [ringsimple]
test 9: completed (287.24 sec)
test 10: initiated [ring]

Also, for the love of $DEITY, can we rename pgm to something useful? This is megacon.

[evan-charmworks]

There is probably overlap with the issues blocking #3021.

[ericjbohm]

Has this been observed recently?

[evan-charmworks]

#3021 still fails