Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Regression tester regressed [baseline] #16286

Closed
tamiko opened this issue Nov 22, 2023 · 1 comment
Closed

Regression tester regressed [baseline] #16286

tamiko opened this issue Nov 22, 2023 · 1 comment
Labels
Regression tester Issues reported by the regression tester bot

Comments

@tamiko
Copy link
Member

tamiko commented Nov 22, 2023

[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:

  • 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]

@tamiko tamiko added the Regression tester Issues reported by the regression tester bot label Nov 22, 2023
@tamiko tamiko pinned this issue Nov 22, 2023
@kinnewig
Copy link
Contributor

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.

So, I wonder why this test worked in the past...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Regression tester Issues reported by the regression tester bot
Projects
None yet
Development

No branches or pull requests

2 participants