Conversation
|
@byrnHDF can you review this PR? This PR modifies the following package(s), for which you are listed as a maintainer:
|
|
@spackbot run pipeline |
|
I've started that pipeline for you! |
|
@spackbot run pipeline |
|
I've started that pipeline for you! |
|
Pipeline errors seem to be related to WRF checksums that should have been fixed by #35401. |
|
@spackbot run pipeline |
|
I've started that pipeline for you! |
|
The latest pipeline still has |
|
I've started that pipeline for you! |
|
@tldahlgren : Rebasing onto |
|
We're having problems with the pipeline builds. Hopefully this gets resolved soon as the |
|
@spackbot run pipeline |
|
I've started that pipeline for you! |
I saw this warning and error in an HDF5-1.14.0 build for
I saw this warning and error in an HDF5 1.14.0 build for radius-aws-aarch64-build: The warning message seems to appear in many of the failing builds in the pipeline. I also noticed in some recent builds on one of our local machines that spack install --keep-stage doesn't seem to be putting anything in the stage directory lately. I don't know what should be doen to change from graviton2 to neovers_n1, though. |
|
The issue with that particular CI run seems to be a build error for |
|
Can this be merged now @alalazo / @eugeneswalker ? |
|
@s-sajid-ali I think this PR is just waiting for CI to finish successfully. Then it'll be auto-merged. |
|
@spackbot run pipeline |
|
I've started that pipeline for you! |
|
@s-sajid-ali Just so you know: by restarting an ongoing CI, you probably gained a longer waiting time 😬 (every pipeline that wasn't finished restarted the same builds from scratch). |
|
@alalazo Thanks for the information. The new CI pipeline has errors for |
|
@spackbot run pipeline |
|
I've started that pipeline for you! |
|
@spackbot run pipeline |
|
I've started that pipeline for you! |
|
Current CI failures are (per this run):
The |
|
The power failures were a node issue, it has been fixed now. Re-running pipeline and they will finish: @spackbot run pipeline |
|
I've started that pipeline for you! |
|
Thanks @eugeneswalker ! The following failures with
Pinging |
|
These should be fixed with #35996 |
|
@spackbot run pipeline |
|
I'm sorry, gitlab does not have your latest revision yet, I can't run that pipeline for you right now. One likely possibility is that your PR pipeline has been temporarily deferred, in which case, it is awaiting a Please check the gitlab commit status message to see if more information is available. Detailspr head: a31d005, gitlab commit parents: ['a5b8066', 'a8bfb0f'] |
|
@spackbot run pipeline |
|
I've started that pipeline for you! |
* HDF5+mpi~fortran * fix style
Fixes #35377