-
Notifications
You must be signed in to change notification settings - Fork 89
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
Failing Albany builds due to changes in Trilinos having to do with the communicators #879
Comments
I just confirmed that this shows up in a regular Albany build w/o spack: https://sems-cdash-son.sandia.gov/cdash/viewBuildError.php?buildid=43483 . |
So, it actually looks like this is due to Trilinos, not Albany. I attempted a fix and am not getting undefined reference errors to utilities in Albany_CommUtils.hpp: https://sems-cdash-son.sandia.gov/cdash/viewBuildError.php?buildid=43484 . I verified that if I check out master Trilinos instead of develop, the problem goes away. After the break, it would be great if someone (@mperego ?, @bartgol ?, @jewatkins ?) can look into this and get the issue resolved. I sadly do not have the bandwidth right now. I will probably switch the nightlies to use master Trilinos for the time being so that they are not failing. As an aside, I don't know whose bright idea it was to merge in a bunch of changes to Trilinos that literally broke everything on multiple levels the day before the shutdown... |
Probably my fix 97930f4 can/should be removed after understanding why there are problems now with the Albany_CommUtilities.cpp and coming up with a real fix. |
Just a wild guess but maybe the tribits snapshot is clashing with our cmake config. Last passing commit ids I see is Albany: 9c32d47, Trilinos: 0270d8bd4cd so it looks like it was after some of the epetra depr. went in. |
Agree, not the best thing to happen right before the shutdown... I think I recall a similar situation happened a few years ago... |
@jewatkins : I agree that the tribits clashing is likely the culprit, esp. given that they just pushed a bunch of changes related to tribits. I feel like we should triage it a bit on the Albany side before we open an issue. If you'd like to volunteer for this (after the break), please speak up. |
I haven't really been following the changes that have been going into Trilinos/Albany but I can try a build after the break if no one else volunteers and the builds are still broken. |
@ikalash, what do you mean by "TriBITS crashing"? Do you mean the HDF5 disable bringing down the configure trilinos/Trilinos#11426? |
I'm not sure what exactly is going on, quite honestly. We made no changes to Albany but are getting undefined reference errors (https://sems-cdash-son.sandia.gov/cdash/viewBuildError.php?buildid=43487) if we build against Trilinos develop now. It doesn't happen when I build against Trilinos master. @lxmota is finding that when he builds LCM against a Trilinos build with MPI enabled, Albany says there was no MPI in Trilinos. Perhaps you have ideas on how your changes could lead to this behavior? I think realistically we will not get the chance to troubleshoot this until after the shutdown on the Albany side. |
@ikalash, okay, let me just put in a PR to back out the Trilinos PR trilinos/Trilinos#11380 for now. I will just need to get someone to approve it. |
@ikalash, I just created trilinos/Trilinos#11428 to revert the changes. I just need a Trilinos GitHub project member to approve the PR and it will merge after PR testing completes. |
Thanks! I'm happy to approve it, if you add me to the list of possible approvers. It doesn't seem I can approve it when I click on it right now. |
The nightly spack build is failing due to the following error:
I suspect it's from the PR merge that was done on 12/22 by @bartgol . Could you please have a look @bartgol (or anyone else)?
It's likely the issue will show up in other nightlies. They just happened to all have failed last night due to some Trilinos failures. I'm fixing it now, so we should know tomorrow.
The text was updated successfully, but these errors were encountered: