[petsc-dev] upcoming release and testing [v2]

[Satish Balay]

I have the following branches for today's next-tmp test.

origin/knepley/fix-dm-gmg
origin/knepley/fix-ex62-tests
origin/knepley/fix-fe-bd-integral
origin/knepley/fix-fe-vector-spaces
origin/knepley/fix-snes-ex69
origin/tisaac/feature-dmfield
origin/hzhang/iscoloring-testvalid
origin/hzhang/superlu_dist-matinertia-hermitian
origin/scott/test-harness-timing2

Karl,

The CUDA tests are hanging/timing-out more often now. For eg:
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/06/examples_next_arch-cuda-double_es.log

And I did see some build where they didn't get killed due to timeout. For eg:
http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/04/05/examples_next_arch-cuda-double_es.log

This is on M2090.  I can see them getting stuck on es.mcs [when I run manually - and check with nvidia-smi]

When i run these tests manually on GTX1050 (frog.mcs) - they zip through..
Any idea why they get stuck on M2090? [more frequently than random hangs..]

thanks,
Satish