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.

Sign up for GitHub

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

Jump to bottom

Framework: Autotester stuck on PR #11547 #11552

Closed
GrahamBenHarper opened this issue Feb 8, 2023 · 2 comments
Closed

Framework: Autotester stuck on PR #11547 #11552

GrahamBenHarper opened this issue Feb 8, 2023 · 2 comments
Assignees
@sebrowne
Labels
autotester Issues related to the autotester. type: bug The primary issue is a bug in Trilinos code or tests

Comments

@GrahamBenHarper
Copy link
Contributor

Bug Report

@trilinos/framework @sebrowne
I pushed a commit right when the AT started testing #11547, and I think it broke. seeing as it has been testing for 19 hours, but #11549 has not yet started testing.

My PR isn't critical since it's just documentation, so it's fine if the testing doesn't go through and the AT gets rebooted or whatever is needed. I just want to point it out before the PRs in the lane pile up.
@GrahamBenHarper GrahamBenHarper added type: bug The primary issue is a bug in Trilinos code or tests autotester Issues related to the autotester. labels Feb 8, 2023
@GrahamBenHarper GrahamBenHarper pinned this issue Feb 8, 2023
@sebrowne
Copy link
Contributor

sebrowne commented Feb 8, 2023

Excellent call, thank you! The Java version requirement was updated yesterday on the automation server, so I had to manually configure all of the nodes to use a newer Java. They're all back online now and running jobs, I'll report back on this tomorrow assuming that stuff runs as expected. I wouldn't be surprised if it has lost track of stuff and anything has been partially running doesn't work the first time.

@sebrowne sebrowne self-assigned this Feb 8, 2023
@GrahamBenHarper
Copy link
Contributor Author

Looks like it just merged #11547 and started testing #11549, so I'll mark this as fixed. Thanks so much @sebrowne!

@GrahamBenHarper GrahamBenHarper unpinned this issue Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sebrowne sebrowne

Labels
autotester Issues related to the autotester. type: bug The primary issue is a bug in Trilinos code or tests
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@GrahamBenHarper @sebrowne