Skip to content

Use develop for spack check#3

Open
sebrowne wants to merge 1 commit into
developfrom
use-develop-for-spack-check
Open

Use develop for spack check#3
sebrowne wants to merge 1 commit into
developfrom
use-develop-for-spack-check

Conversation

@sebrowne

@sebrowne sebrowne commented May 19, 2025

Copy link
Copy Markdown
Owner

@trilinos/

Motivation

Stakeholder Feedback

Testing

@sebrowne
Update to current Spack develop
f93e824 
This runs the risk of not using the already-installed packages due to
concretization changes, but that may not be a huge deal.  Also the
config files may not be compatible.  Will see.

Signed-off-by: Samuel E. Browne <sebrown@sandia.gov>
@github-actions

github-actions Bot commented May 19, 2025

Copy link
Copy Markdown

CDash for AT1 results [Only accessible from Sandia networks]
CDash for AT2 results [Currently only accessible from Sandia networks]

@sebrowne sebrowne force-pushed the use-develop-for-spack-check branch from 11cfe2b to f93e824 Compare June 23, 2025 16:04
@github-actions

github-actions Bot commented Jun 24, 2026

Copy link
Copy Markdown

This Pull Request has been marked for closure due to inactivity.
Because of the changing nature of the Trilinos source due to active development, a pull request with no activity for 365 days is considered to be abandoned and will be automatically closed after 30 additional days of inactivity from when it was marked inactive.
If this should be kept open, please post a comment and/or remove the label MARKED_FOR_CLOSURE to reset the inactivity timer.
If it is ok for this pull request to be closed, feel free to go ahead and close it. Please do not add any comments or change any labels or otherwise touch this issue unless your intention is to reset the inactivity counter for an additional year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

MARKED_FOR_CLOSURE

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@sebrowne