-
Notifications
You must be signed in to change notification settings - Fork 578
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tempus: Test failures with Tpetra's deprecated code disabled #5616
Comments
@kddevin can you assign the Trilinos developer that was going to look at this? |
How did this get through testing and get committed? @kddevin We need this fixed in the next day or two as it is holding up my development and develop on EMPIRE. If this is not possible, the offending commit needs to be reverted as soon as possible. Sorry but this is really a problem. |
Hmm... I pulled develop yesterday, and seemed to get errors related to this?! This there some other problem? |
I'm not sure about any other problems. The tests above fail when |
Ok sounds good. I will take a closer look at the failures with my develop build. Thanks for the clarification! |
So ... here is what I am seeing on my Mac OS 10.14 with Trilinos develop (90b0f99)
and
Is just a problem on the Mac? This is a clean build and I have attached my configure and build logs. |
I haven't seen that particular error. @william76 could this be related to ETI work in @trilnos/xpetra ? |
This sounds like a problem in the Xpetra instantiation work that @william76 and @trilinos/xpetra are doing. It would be unrelated to the Tpetra deprecation. |
I think @brian-kelley will be helping with the Tpetra deprecation work. |
@ccober6 @kddevin I believe I have this fixed already in my branch for PR #5605 that I'm working on related to the bug reported in #5591 but I haven't let that PR go in because tracking down the errors with ETI off has been more stubborn than I'd like. Also, building without ETI takes a long time :( Hopefully I can get this PR in later today or tomorrow. |
Now y'all know how the Sierra developers feel ;-) |
Maybe we can move further ETI discussion elsewhere, as it isn't related to the deprecation issue here. |
@tjfulle I am having difficulty reproducing the deprecation failures you are seeing in @trilinos/tempus My tempus tests are running now; several that were reported as failing are now passing. Perhaps your rebase from develop pulled in fixes to the test failures. So @trilinos/tempus team, please wait until we confirm or refute the failures before spending time on this issue. |
I merged in #5605 which should fix the The recent Xpetra classes that I pushed through were |
@kddevin - maybe one of the other fixes had the happy consequence of fixing these too? I ran the GO=int tests a couple weeks ago and haven’t looked at them since all the recent work. |
Ok sounds good. FYI, as of a few minutes ago, I was still seeing the next set of errors on develop. Thoughts?
|
@brian-kelley Can you take a look at the compilation Curt is seeing above? It is unrelated to Tpetra deprecation, but this github issue has gone way off course anyway. :) |
@ccober6 I can't seem to replicate the Ifpack2 build error. I'm on up-to-date develop (a4f99ce), on AppleClang 10.0.0 with OpenMPI 4.0.1. I took the configure script you linked and didn't get the error, then I added the lines to disable Xpetra/Tpetra deprecated code and still didn't get it. If I roll back to 90b0f99 then I get the BlockedMultiVector error you ran into first. Can you link the exact version and configure script? |
@brian-kelley Ok, I just rebuilt with a4f99ce on my Mac and it compiled and ran correctly. My previous build was 1bfa7b1 (between a4f99ce and 90b0f99). :( But I guess it does not matter at this point. Thanks for the help! |
@tjfulle it looks like this might have been resolved, should this issue be closed out? |
Bug Report
@trilinos/tempus
Part of: #5602
Description
With Tpetra's deprecated code disabled, many Tempus tests fail for
GlobalOrdinal=int
:See the full configuration for
GlobalOrdinal=int
at #5602 (comment)Note: if you work off of the Trilinos develop branch, you will likely get build errors using the above linked configurations. The branch tjfulle:issue-5536 is currently working.
The text was updated successfully, but these errors were encountered: