Scott Wittenburg
Scott Wittenburg
Maybe that error you saw was temporary @brugger1? I just ran the reproducer and encountered the what appears to be the same error I pasted in slack: ``` 1 error...
@spackbot fix style
@spackbot fix style
@spackbot run pipeline
I suspect if github can't make a merge commit because of the unresolved conflicts, the sync script isn't going to push your branch to gitlab for testing.
> Ugh. `gptune` in the `e4s-pr-build` is the only one failing (again). Looks like `gptune` timed out three times in that pipeline, and the timeout is 6hrs. It would probably...
Restoring the `--only package` option because dependencies were installed from source in the last pipeline is not the right thing to do. The problem was that the AWS credentials had...
> @spackbot style --fix That looks like the appropriate spack command, but to get spackbot to respond, you have to do it like [this](https://github.com/spack/spack/pull/31878).
I think we have seen this once before, but I will verify to be sure it's the same case. In that case, two different stacks build the same hash, and...
Following up to confirm that the `.spec.json.sig` file for `openblas /c55doyb` from `s3://spack-binaries/develop` matches exactly the one from `s3://spack-binaries/develop/radiuss`, while the `.spack` file for `openblas /c55doyb` file from `s3://spack-binaries/develop` matches...