You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have opened this issue because I encountered an unclean regression run compared to the baseline, but
I was unable to identify a regression between the current run and the previous run of the regression testsuite. This is likely due to one of the following two reasons:
The previous testsuite run is incomplete and I thus cannot infer that the regressions occurred between the current and previous run.
The previous testsuite run had configure or build failures for a configuration, and the current testsuite run shows configure, build warnings, or failing tests.
In this case I cannot infer when those failures have been introduced exactly and resort to opening a less specific issue.
I will close and unpin this issue automatically once a full run is complete and compares cleanly to the baseline.
[end automated regression testsuite report]
The text was updated successfully, but these errors were encountered:
These errors are interesting.
As far as I understand this problem, this error is caused by the operator= of the TperaWrappers::Vector.
While working on the Tpetra wrappers, I already observed that the original operator= does not work in parallel.
[start automated regression testsuite report]
Dear all,
this is the automated regression testsuite reporting an unclean regression run compared to the baseline.
Summary:
Previous 5 testsuite runs:
Last 5 regression test reports:
Notes:
In this case I cannot infer when those failures have been introduced exactly and resort to opening a less specific issue.
[end automated regression testsuite report]
The text was updated successfully, but these errors were encountered: