Add working spack build with build cache. #695
Conversation
|
FYI, one of the spack ubuntu builds fails. |
|
@cameronrutherford CURL cannot be found from the path (see here), but I see spack has specified to install curl. |
Yes... not really sure what's going on but I haven't had time to try and debug. I'm thinking if we let spack build curl this will resolve as the bug is with using external curl. Just need to exclude it the same way we exclude finding Python.. |
|
it loads curl and openssl, but now fails with |
|
spack/spack#46378 - I thought this would fix the issue. I think it's a reasonable fix to the spack package, but didn't resolve the issue. What's frustrating here is that the error log isn't printing it's full output. I can't even see the full CMake line. I went down this path because there was an extra GitHub actions further complicates the problem because it's all running inside a VM, so unless I spend money on Azure it's hard to reproduce. I will take a look again later with a fresh perspective and see what I can figure out. Confusing why we are only seeing this sort of issue with HiOp, not ExaGO or other packages... |
|
This time fails with If it is too cumbersome to make this work, then I suggest to disable this build. All the functionality is tested by the LLNL CI. |
I can't believe I missed it, but we simply weren't cloning the repo in the spack pipelines. The pipelines are really flying here and complete in ~5 minutes |
|
MPI CPU builds are running, passing tests and being pushed to a buildcahe for each branch in your repo. All in under 5 minutes if we don't have to re-build dependencies! |
| skopeo inspect \ | ||
| docker://$OCI_URL \ | ||
| --raw \ | ||
| --creds "${{ env.USERNAME }}:${{ secrets.GITHUB_TOKEN }}" \ |
There was a problem hiding this comment.
where do we provide the token?
I'd like to learn more about how you create the user hiop-bot and the dependencies in the container, but we can do it offline.
| jobs: | ||
| base_image_build: | ||
| runs-on: ubuntu-24.04 | ||
| permissions: |
There was a problem hiding this comment.
@nychiang tokens are automatically created by pipelines with permissions based on this YAML config.
| TMPDIR: /opt/spack-cache | ||
| # Our repo name contains upper case characters, so we can't use ${{ github.repository }} | ||
| IMAGE_NAME: hiop | ||
| USERNAME: hiop-bot |
There was a problem hiding this comment.
@nychiang name is arbitrary. You can pick a different name 😁
| && rm -rf /var/lib/apt/lists/* | ||
| RUN add-apt-repository ppa:ubuntu-toolchain-r/test && \ | ||
| apt-get install -y --no-install-recommends \ | ||
| gfortran \ |
There was a problem hiding this comment.
@nychiang gfortran was needed to launch MPI based applications when I was doing this for ExaGO.
I admittedly didn't pull/test the HiOp images, but this is covered in the tutorial I followed https://github.com/spack/spack-tutorial/blob/main/tutorial_binary_cache.rst#creating-runnable-container-images
There was a problem hiding this comment.
Figuring out the dependencies was admittedly trial and error.
For ExaGo, I was running MPI enabled OPFLOW to get our --version output, and logically added to the base image from the error messages I got.
Closes #601