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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Revive Albany + Dakota in at least one nightly build #462

Closed
ikalash opened this issue Mar 31, 2019 · 2 comments
Closed

Revive Albany + Dakota in at least one nightly build #462

ikalash opened this issue Mar 31, 2019 · 2 comments

Comments

@ikalash
Copy link
Collaborator

ikalash commented Mar 31, 2019

This is a spin-off from #456 . If we want to keep the Dakota executables, we need Albany + Dakota tested in at least one nightly build. This used to happen in my builds, but hasn't been for awhile (year or two).

@ikalash
Copy link
Collaborator Author

ikalash commented Mar 31, 2019

I'm not able to compile Trilinos + the most recent version of Dakota (through TriKota) on my workstation - I've opened an issue to get some help with this from the TriKota team: trilinos/Trilinos#4771 .

ikalash added a commit that referenced this issue Apr 1, 2019
towards issue #462.

All Dakota tests currently seg fault - need to look into and resolve this.
ikalash added a commit that referenced this issue Apr 1, 2019
to clone/build Dakota/TriKota, and applying a patch needed to
get this build to work.
@ikalash
Copy link
Collaborator Author

ikalash commented Apr 2, 2019

I revived these in the tests on camobap.

@ikalash ikalash closed this as completed Apr 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant