Regression tester regressed d97197

[tamiko]

[start automated regression testsuite report]

Dear all,

this is the automated regression testsuite reporting a new regression between

• new revision: d971973 regression testsuite results
• old revision: df8d02a regression testsuite results

Summary:

• 😠 new test failures introduced for configuration GNU-13.2.0-master-debian-13 on site tester-tng

I have identified the following pull requests as possible candidates:

• Rename a poorly named variable. #16971 (authored-by: @bangerth; merged-by: @masterleinad)
• Make finite element objects 'const'. #16968 (authored-by: @bangerth; merged-by: @kronbichler)
• Clarify a comment in step-77. #16969 (authored-by: @bangerth; merged-by: @kronbichler)
• NonMatching::FEValues: accept CellAccessor #16932 (authored-by: @peterrum; merged-by: @drwells)

Notes:

• The regression reported above is a subset of the following full set of regressions compared to the baseline:
  • 😠 test failures for configuration GNU-13.2.0-master-debian-13 on site tester-tng
  • 😞 build warnings for configuration GNU-9.4.0-master-ubuntu-lts-20.04 on site tester-tng
• I will close and unpin this issue automatically once a full run is complete and compares cleanly to the baseline.
• If closed I will reopen the issue if the testsuite run identified an additional regression compared to what I have reported so far.

[end automated regression testsuite report]

[bangerth]

These are all MPI-related tests (including a bunch of SCALAPACK tests) whose failure seems unrelated to the PRs mentioned above. None of the tests produced any output. I suspect this to be spurious.

[tamiko]

@bangerth Yes, the entire compute cluster died. I am surprised it got the report sent out at all.