Regression tester regressed 9c9a7d

[tamiko]

[start automated regression testsuite report]

Dear all,

this is the automated regression testsuite reporting a new regression between

• new revision: 9c9a7d9 regression testsuite results
• old revision: 7d8aab4 regression testsuite results

Summary:

• 😞 new build warnings introduced for configuration GNU-9.4.0-master-ubuntu-lts-20.04 on site tester-tng
• 😞 new build warnings introduced for configuration GNU-13.1.1-master-64bit_indices-20230507 on site tester-tos
• 😠 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:

• Add parallel support to TpetraWrappers::Vector. #16290 (authored-by: @kinnewig; merged-by: @kronbichler)
• Use p[index] instead of p(index) for class Point. #16488 (authored-by: @bangerth; merged-by: @blaisb)

Notes:

• The regression reported above is a subset of the following full set of regressions compared to the baseline:
  • 😞 build warnings for configuration GNU-9.4.0-master-ubuntu-lts-20.04 on site tester-tng
  • 😠 test failures for configuration Clang-16.0.6-master-autodetection-20230507 on site tester-tos
  • 😠 test failures for configuration Clang-16.0.6-master-sanitizer-20230622 on site tester-tos
  • 😞 build warnings for configuration GNU-13.1.1-master-64bit_indices-20230507 on site tester-tos
  • 😠 test failures for configuration GNU-13.1.1-master-64bit_indices-20230507 on site tester-tos
  • 😠 test failures for configuration GNU-13.1.1-master-autodetection-20230507 on site tester-tos
  • 😠 test failures for configuration GNU-13.1.1-master-minimal-20230116 on site tester-tos
  • 😠 test failures for configuration GNU-13.1.1-master-standalone_kokkos-20230507 on site tester-tos
  • 😠 test failures for configuration GNU-13.1.1-master-std=c++20-20230626 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]