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

Update spack_build.yml to fix cmake pulling llvm #698

Merged
merged 6 commits into from
Nov 11, 2024
Merged

Update spack_build.yml to fix cmake pulling llvm #698

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
ac20b3d
Update spack_build.yml to fix cmake pulling llvm
cameronrutherford Nov 6, 2024
4315931
Update spack_build.yml to specify cmake requirements for all packages…
cameronrutherford Nov 7, 2024
0c1e55f
Move openblas into direct package spec
cameronrutherford Nov 7, 2024
a486ada
Specify openblas in a different way
cameronrutherford Nov 7, 2024
7ba7b00
Try re-using builds for quicker pipelines
cameronrutherford Nov 7, 2024
d07cab2
Add some comments and move libevent version spec
cameronrutherford Nov 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions .github/workflows/spack_build.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -99,9 +99,9 @@ jobs:
strategy:
matrix:
spack_spec:
- hiop@develop+mpi~raja~shared~kron~sparse ^openblas ^openmpi
- hiop@develop~mpi~raja~shared~kron~sparse ^openblas
- hiop@develop~mpi+raja~shared~kron~sparse ^openblas
- hiop@develop+mpi~raja~shared~kron~sparse ^openmpi
- hiop@develop~mpi~raja~shared~kron~sparse
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nychiang this build is failing because for some reason it's trying to build libflame, and not openblas.

Looks at the concretization comparison between builds, and you'll see that a 3 hour build would make no sense for the smallest build of the batch here.

Copy link
Collaborator Author

@cameronrutherford cameronrutherford Nov 7, 2024 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why would that spec possibly need python for this build?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

python is required via
hiop -> amdlibflame -> aocl-utils -> doxygen -> graphviz -> gtkplus -> meson -> python-xxx
why do we need amdlibflame? Concretization shows that it installs a lot of packages.
@cameronrutherford

- hiop@develop~mpi+raja~shared~kron~sparse

# We will need coinhsl for this, but what are the rules for using
# a coinhsl tarball?
Expand Down Expand Up @@ -129,9 +129,12 @@ jobs:
cat << EOF > spack.yaml
spack:
specs:
- ${{ matrix.spack_spec }} ^libevent~openssl target=x86_64_v2
- ${{ matrix.spack_spec }} target=x86_64_v2
- openblas
- libevent~openssl
concretizer:
reuse: dependencies
reuse: false
unify: true
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hopefully this gets openblas to always be built...

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I got what I wanted... I meant to just have openblas be a part of the concretization, but it appears as though it's always building from source now, and not pulling from the cache. I think reverting to ^openblas in the spec might fix this... I also am trying to better remember where libevent gets pulled in, but I digress.

config:
source_cache: $SPACK_CACHE/source_cache
misc_cache: $SPACK_CACHE/misc_cache
Expand Down
Loading