-
Notifications
You must be signed in to change notification settings - Fork 575
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
Framework: Create Build for ETI OFF #5729
Comments
With changing the Trilinos default to ETI ON, we will need to add a build with ETI off, or we will lose the ability to build with ETI off. @kddevin mentioned this recently as well. I suggest one of the dev->master builds. I propose the Clang 9 build, but I am open to any other suggestions. |
We discussed this at the framework stand up today. |
Best practice with an ETI OFF test would be to enable "weird" types, just to make sure that downstream dependency inversion for factories is working correctly. |
@mhoemmen what are you referring to exactly with "weird types"? |
I've tested a few things with ETI OFF using GCC 7.2.0 and clang 9.0.0. There are a significant amount of errors for both. It seems we're primarily running into issues in @trilinos/tempus with a few problems in @trilinos/piro and @trilinos/rol and some odd issue in @trilinos/muelu, @trilinos/shylu, @trilinos/ifpack2, and @trilinos/xpetra. Though there are likely more hiding behind the 50 error limiter. |
@ZUUL42 I randomly sampled the MueLu errors, which are all in the tests. They are of the type
I don't know what could be causing this. You might try reducing the |
FYI, I built Tempus with ETI=OFF on my mac and got the same errors that are produced above. We are investigating. |
@ZUUL42 wrote:
I should have clarified: types that are not enabled by default in ETI=ON builds. This will test run-time registration of solver factories for the ETI=OFF case. |
@jhux2, I've trying setting CMAKE_BUILD_PARALLEL_LEVEL to 2 with no change in results. |
FYI, the Tempus failures should be fixed in the next day or so with #8549. Just waiting on a review. |
#8549 has been merged, so you should not see any Tempus failures for ETI=OFF. |
I've run a build of ETI Off with the Master Merge PR Clang 9.0.0 build.
|
@ZUUL42 MueLu build errors should be fixed. |
@cgcgcg thanks. |
Query to show all eti_off test builds. CDash |
Looks like some issue in KokkosKernels is now causing a lot of stuff in MueLu to fail? |
@cgcgcg Looks like we are getting close on this now. Down to on 2 Build Errors from @trilinos/trilinoscouplings and a some test failures from @trilinos/muelu, @trilinos/trilinoscouplings, & @trilinos/panzer. If we can at least get the @trilinos/trilinoscouplings error fixed, we have the option of fixing or turning off the tests failing for this build. |
@ZUUL42 These cmake warnings look a bit scary:
|
@jhux2, I'll look into that. |
@ZUUL42 I fixed one of the 2 build errors. The other one looks like the OOM killer might have gotten the compiler. On my workstation, I had to reduce the build parallelism to avoid the issue. |
@trilinos/belos @hkthorn @jennloe @iyamazaki I don't understand the Belos solver registration well enough to fix these test failures. Looks like essentially no Belos solvers are registered, yet none of the Belos tests fail. Are Xpetra solvers different from Epetra/Tpetra solvers? |
FYI, it appears there are new errors from Ifpack2 if tests are enabled - it's due to the unit tests. I opened a separate issue on this #9280 . These just cropped up end of last week with an Ifpack2 PR that went in. |
I ran another test build the other day, forgot to post right away. (whoops, sorry) This is from Jun 18. |
Looks like OOM, no? |
@cgcgcg, that's what I'm finding. |
@ZUUL42 I assume
|
Based on feedback from the Trilinos Product Lead team, we are pressing pause on this effort and will likely discontinue trying to support this option. We need to socialize this more before making a final decision. |
I was unable to see the latest CDash results. @ZUUL42 do you remember how many packages were failing? Could we turn a few packages off and get a clean build? There is renewed concern about this. |
@jwillenbring here's a couple new ETI OFF builds. |
Kicked off a couple more builds. The same link will pick them up. |
@ZUUL42 You might try a different compiler, such as gcc, which presumably would have different memory requirements (if memory is what's causing the internal compiler error). |
@jhux2 I can do that. Though I'm not sure if there was a reason Clang was specifically chosen for the ETI OFF build or not. |
@ZUUL42 I'm just thinking of how to avoid what appears to be an out-of-memory error with the compiler. The builds are all |
The MueLu tests were failing due to a bug in Belos, not due to OOM, no? |
@jhux2 I'm not familiar with those flags. |
@ZUUL42 You only want |
Looks like debug symbols are also switched on here:
|
Clang 10 Build 3272 adds: |
@ZUUL42 This is progress, right? The MueLu tests that previously didn't compile now do, right? |
Migrated to Jira. |
Enhancement
@trilinos/framework
Create build that sets disables explicit instantiation (ETI).
This may first be tried in dev->master.
The text was updated successfully, but these errors were encountered: