If you run the full test suite and have failures, you get something like this: # # To rerun failed tests: # make -f gmakefile test test-fail=1 This was turned off for non-full-test cases (search and query cases) in the MR that reduced test harness verbosity. I think what you are wanting is to turn it back on for all cases with this message: # # To rerun all failed tests in debugger: # make -f gmakefile test test-fail=1 DEBUG=1 Is that correct? This is a 2 line fix in `config/report_tests.py` if I understand this correctly. Scott P.S. Please don't forget the help target. It's actually helpful: make -f gmakefile.test help On 2021-03-29 23:25, Barry Smith did write:

# FAILED snes_tutorials-ex12_quad_hpddm_reuse_threshold snes_tutorials-ex12_p4est_nc_singular_2d_hpddm snes_tutorials-ex56_hpddm snes_tutorials-ex12_quad_hpddm_reuse_threshold_baij sys_tests-ex53_2 snes_tutorials-ex12_quad_hpddm_reuse_baij snes_tutorials-ex12_quad_hpddm_reuse snes_tutorials-ex12_p4est_singular_2d_hpddm snes_tutorials-ex12_tri_parmetis_hpddm snes_tutorials-ex12_quad_singular_hpddm sys_tests-ex26_1 sys_tests-ex26_2 snes_tutorials-ex12_tri_parmetis_hpddm_baij snes_tutorials-ex12_tri_hpddm_reuse_baij snes_tutorials-ex12_tri_hpddm_reus

Scott,

Any thoughts on how the test harness could tell the developer exactly how to reproduce a problematic cases in the debugger without them digging around in the code to check arguments etc.

So for example "Run: mpiexec -n N ./xxx args -start_in_debugger" to reproduce this problem? Then one could just cut and paste and be debugging away.

Thanks

Barry

-- Scott Kruger Tech-X Corporation [email protected] 5621 Arapahoe Ave, Suite A Phone: (720) 466-3196 Boulder, CO 80303 Fax: (303) 448-7756