Regression tester regressed b728a7

[tamiko]

[start automated regression testsuite report]

Dear all,

this is the automated regression testsuite reporting a new regression between

• new revision: b728a79 regression testsuite results
• old revision: acb749f regression testsuite results

Summary:

• 😠 new test failures introduced for configuration GNU-13.1.1-master-64bit_indices-20230507 on site tester-tos

I have identified the following pull requests as possible candidates:

• Declare conversion assignments for Tpetra vectors. #16663 (authored-by: @kinnewig; merged-by: @masterleinad)
• Added complex sparse matrix instantiations. #16641 (authored-by: @MalikScheifinger; merged-by: @masterleinad)

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.1.1-master-64bit_indices-20230507 on site tester-tos
• 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]

multigrid/renumbering_08.mpirun=2.debug died with a segfault. Does that sound familiar to anyone?

[kronbichler]

I did not see that test failing before, but it happens right in the middle, so there might be something going on. Let me run it locally with valgrind to see if there is, by chance, some hidden memory problem.

[kronbichler]

I don't see anything suspicious, and there were no recent changes in related areas as far as I can see, so I believe this must be spurious.

[tamiko]

[automated regression testsuite]

Regression tester reported a clean run compared to baseline. 😊
Closing all issues. 😎

• revision: 38edccc regression testsuite results