summaryrefslogtreecommitdiff
path: root/share
AgeCommit message (Collapse)AuthorFilesLines
2024-10-15Reduce noop job resource requests (#46920)Caetano Melone1-2/+2
`no-spec-to-rebuild` jobs use far less resources than they request. For example, [this](https://gitlab.spack.io/spack/spack/-/jobs/12944487) job [used](https://prometheus.spack.io/api/v1/query_range?query=container_memory_working_set_bytes{pod=%22runner-dcsgp53u-project-2-concurrent-3-0ubclrr1%22}&start=1728655743&end=1728656543&step=1s) around 3MB. While this won't lead to any crazy cost savings, k8s requests effectively block other jobs from using the resources, so reducing this to a reasonable number is important.
2024-10-15env depfile: generate Makefile with absolute script path (#46966)Tobias Ribizel1-1/+1
Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>
2024-10-14Don't require OIDC initialization for noop (#46921)kwryankrattiger1-0/+1
ref. https://github.com/spack/spack-infrastructure/pull/957
2024-10-10Use pcluster-alinux2 container image with pre-installed compilers (#44150)Stephen Sachs6-70/+76
2024-10-04`gc`: restrict to specific specs (#46790)Todd Gamblin2-1/+7
`spack gc` has so far been a global or environment-specific thing. This adds the ability to restrict garbage collection to specific specs, e.g. if you *just* want to get rid of all your unused python installations, you could write: ```console spack gc python ``` - [x] add `constraint` arg to `spack gc` - [x] add a simple test Signed-off-by: Todd Gamblin <tgamblin@llnl.gov>
2024-10-03Noop jobs should do less work (#46732)kwryankrattiger1-0/+4
2024-10-02fix 'command -v' not in csh (#45845)Ray Huang1-2/+2
2024-09-30Update and standardize implementation of RADIUSS packages (#45648)Adrien Bernede1-2/+3
* Add latest releases of Camp, RAJA, Umpire, CHAI and CARE * Address review comments + blt requirement in Umpire * CARE @develop & @main: Submodules -> False * Changes in Umpire * Changes in RAJA * Changes in CHAI * Changes in RAJA: prefer 'spec.satisfies' to 'in spec' This is due to a non-equivalence in Spack with providers like mpi. See e.g. https://github.com/spack/spack/pull/46126 * Changes in Umpire: prefer 'spec.satisfies' to 'in spec' This is due to a non-equivalence in Spack with providers like mpi. See e.g. https://github.com/spack/spack/pull/46126 * Changes in CARE: Still need to update to CachedCMakePackage based on RADIUSS Spack Configs version * Missing change in RAJA + changes in fmt * Fix synta * Changes in Camp * Fix style * CHAI: when ~raja, turn off RAJA in build system * Fix: Ascent@0.9.3 does not support RAJA@2024.07.0 * Enforce same version constraint on Umpire as for RAJA * Enforce preferred version of vtk-m in ascent 0.9.3 * Migrate CARE package to CachedCMakePackage * Fix style in CARE package * CARE: Apply changes for uniform implementation accross RADIUSS projects * Caliper: move to CachedCMakePackage, from RADIUSS Spack Configs * Adapt RAJA Perf to spack CI * Activate CHAI, CARE and RAJAPerf in Spack CI * Fixes and diffs with RADIUSS Spack Configs * Caliper: fix * Caliper : fix + RAJAPerf : style * RAJAPerf: fixes * Update maintainers * raja-perf: fix license header * raja-perf: Fix variant naming openmp_target -> omptarget * raja-perf: style and blt dependency versions * CARE: benchmark and examples off by default (like tests) * CARE: fix missing variable * Update var/spack/repos/builtin/packages/raja-perf/package.py * CARE: fix branch name * Revert changes in MFEM to pass CI * Fix CXX17 condition in RAJA + add sycl option in RAJAPerf --------- Co-authored-by: Rich Hornung <hornung1@llnl.gov>
2024-09-26developer-tools-ci: remove version constraint on Emacs (#46590)Alec Scott1-1/+1
2024-09-24ML CI: Ubuntu 22 -> 24 (#45644)Adam J. Stewart4-12/+10
2024-09-19run-unit-tests: no xdist if coverage (#46480)Harmen Stoppels1-3/+3
xdist only slows down unit tests under coverage
2024-09-17cloud_pipelines/.gitlab-ci.yml: run spack arch (#46437)Harmen Stoppels1-0/+1
2024-09-16Revert "allow failure for cray-sles (#46411)" (#46413)kwryankrattiger1-1/+0
This reverts commit 576251f0dad79d0e69f73eb393ce40a0921df0b4.
2024-09-16allow failure for cray-sles (#46411)Harmen Stoppels1-0/+1
2024-09-13Optionally output package namespace (#46359)Kyle Knoepfel2-2/+4
2024-09-12e4s rocm external ci stack: upgrade to rocm v6.2.0 (#46328)eugeneswalker2-76/+76
* e4s rocm external ci stack: upgrade to rocm v6.2.0 * magma: add rocm 6.2.0
2024-09-10bugfix: `elfutils` has no bzip2 or xz variants (#46294)Todd Gamblin1-1/+1
Signed-off-by: Todd Gamblin <tgamblin@llnl.gov>
2024-09-09gptune: new test API (#45383)AcriusWinter1-1/+0
* gptune: new test API * gptune: cleanup; finish API changes; separate unrelated test parts * gptune: standalone test cleanup with timeout constraints * gptune: ensure stand-alone test bash failures terminate; enable in CI * gptune: add directory to terminate_bash_failures * gptune/stand-alone tests: use satisifes for checking variants --------- Co-authored-by: Tamara Dahlgren <dahlgren1@llnl.gov>
2024-09-06use updated container with cmake@3.30.2 (#46262)eugeneswalker2-2/+2
2024-09-06Bootstrap GnuPG and `file` on Windows (#41810)John W. Parent3-2/+6
Spack can now bootstrap two new dependencies on Windows: GnuPG, and file. These dependencies are modeled as a separate package, and they install a cross-compiled binary. Details on how they binaries are built are in https://github.com/spack/windows-bootstrap-resources
2024-09-06fish: use shlex.quote instead of custom quote (#46251)Harmen Stoppels1-45/+45
2024-09-05spack deprecate: deprecate --link-type flag (#46202)Harmen Stoppels1-1/+1
2024-09-02e4s ci stacks: add geopm-runtime (#45881)eugeneswalker3-3/+2
2024-08-30windows-vis: vtk~mpi (#46133)Harmen Stoppels1-1/+1
2024-08-30cray: allow failure due to broken blas (#46111)Harmen Stoppels1-0/+2
1. libsci_cray.so is broken, as it fails to list `libdl.so` in DT_NEEDED. 2. cray compilers fail to build a different blas
2024-08-27lammps: improve FFT selection and add fft_kokkos variant (#45969)Nick Hagerty1-2/+2
2024-08-22Make spack compiler find use external find (#45784)Massimiliano Culpo2-4/+8
so that there is no duplicate detection logic for compilers
2024-08-19Remove deprecated `--safe-only` in spack version cmd (#45765)Alec Scott2-4/+2
2024-08-18WarpX: Python on pyAMReX (#45251)Axel Huebl8-10/+10
* WarpX: Python on pyAMReX Long overdue update for WarpX: in 2024, we updated our Python bindings to rely on the new pyAMReX package. This deprecates the old `py-warpx` package and adds a new dependency and variant to WarpX. Also deprecates old versions that we will not continue to support. * Update Cloud/E4S Pipelines for WarpX `py-warpx` is replaced by `warpx +python` oneAPI does not support IPO/LTO: diable for `py-amrex` even though pybind11 strongly encourages it.
2024-08-16e4s ci: add wrf (#45719)eugeneswalker4-0/+8
* e4s ci: add wrf * e4s ci: also add wrf companion/adjacent package wps * e4s oneapi: comment out wps: %oneapi not supported?
2024-08-16Run unit test in parallel again in CI (#45793)Massimiliano Culpo1-1/+1
The --trace-config option was failing for linux unit-tests, so we were running serial.
2024-08-14e4s ci: add chapel (#45659)eugeneswalker5-2/+14
* e4s ci: add chapel * e4s ci: fix gpu target typo Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com> --------- Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
2024-08-14spack buildcache push: parallel in general (#45682)Harmen Stoppels2-4/+4
Make spack buildcache push for the non-oci case also parallel, and --update-index more efficieny
2024-08-13spack buildcache push: best effort (#45631)Harmen Stoppels2-4/+12
"spack buildcache push" for partially installed environments pushes all it can by default, and only dumps errors towards the end. If --fail-fast is provided, error out before pushing anything if any of the packages is uninstalled oci build caches using parallel push now use futures to ensure pushing goes in best-effort style.
2024-08-12remove config:concretizer:clingo (#45684)Harmen Stoppels3-3/+0
2024-08-10Remove the old concretizer (#45215)Massimiliano Culpo1-5/+0
The old concretizer is still used to bootstrap clingo from source. If we switch to a DAG model where compilers are treated as nodes, we need to either: 1. fix the old concretizer to support this (which is a lot of work and possibly research), or 2. bootstrap `clingo` without the old concretizer. This PR takes the second approach and gets rid of the old concretizer code. To bootstrap `clingo`, we store some concrete spec prototypes as JSON, select one according to the coarse-grained system architecture, and tweak them according to the current host. The old concretizer and related dead code are removed. In particular, this removes `Spec.normalize()` and related methods, which were used in many unit-tests to set up the test context. The tests have been updated not to use `normalize()`. - [x] Bootstrap clingo concretization based on a JSON file - [x] Bootstrap clingo *before* patchelf - [x] Remove any use of the old concretizer, including: * Remove only_clingo and only_original fixtures * Remove _old_concretize and _new_concretize * Remove _concretize_together_old * Remove _concretize_together_new * Remove any use of `SPACK_TEST_SOLVER` * Simplify CI jobs - [x] ensure bootstrapping `clingo` works on on Darwin and Windows - [x] Raise an intelligible error when a compiler is missing - [x] Ensure bootstrapping works on FreeBSD - [x] remove normalize and related methods Signed-off-by: Todd Gamblin <tgamblin@llnl.gov>
2024-08-09Remove execution permission from setup-env.sh (#45641)Dominic Hofer6-0/+0
`setup-env.sh` is meant to be sourced, not executed directly. By revoking execution permissions, users who accidentally execute the script will receive an error instead of seeing no effect. * Remove execution permission from `setup-env.sh` and friends * Don't make output file executable in `spack commands --update-completion` --------- Co-authored-by: Todd Gamblin <tgamblin@llnl.gov> Signed-off-by: Todd Gamblin <tgamblin@llnl.gov>
2024-08-01e4s oneapi ci: try enabling some disabled specs (#45355)eugeneswalker1-24/+25
2024-07-24CI: add ML ROCm stack (#45302)afzpatel2-0/+116
* add ML ROCm stack * add suggested changes * remove py-torch and py-tensorflow-estimator * add TF_ROCM_AMDGPU_TARGETS env variable and remove packages from pipeline * remove py-jax and py-xgboost
2024-07-23e4s rocm external ci stack: upgrade to v6.1.2 (#45356)eugeneswalker2-76/+76
* e4s rocm external ci stack: upgrade to v6.1.2 * magma: add rocm-core 6.1.2
2024-07-18e4s ci: enable some disabled specs (#44934)eugeneswalker2-127/+86
* e4s ci: enable some disabled specs * comment out cp2k +cuda due to unsupported cuda_arch * comment out dealii+cuda due to concretize error * work through concretize errors * e4s: comment out failing builds * e4s stack: disabled non-building specs * comment out failing specs * comment out failing specs * cleanup comments
2024-07-17Add `depends_on([c,cxx,fortran])` (#45217)Harmen Stoppels2-2/+1
Add language dependencies `c`, `cxx`, and `fortran`. These `depends_on` statements are auto-generated based on file extensions found in source tarballs/zipfiles. The `# generated` comment can be removed by package maintainers after validating correctness.
2024-07-12bootstrap ci: add exit code validation for windows (#45221)John W. Parent1-1/+1
2024-07-11Buildcache: remove deprecated --allow-root and preview subcommand (#45204)Tamara Dahlgren2-25/+5
2024-07-09`spack find -c`: search all concretized-but-not-installed specs (#44713)Peter Scheibel2-2/+4
Originally if you had `x -> y -> z`, and an env with `x` in its speclist that is concretized but not installed, then `spack find -c y` would not show anything. This was intended: `spack find` has up-until-now only ever listed out installed specs (and `-c` was for adding a preamble section about roots). This changes `spack find` so: * `-c` makes it search through all concretized specs in the env (in a sense it is anticipated that a concretized environment would serve as a "speculative" DB and users may want to query it like they query the DB outside of envs) * Adds a `-i/--install-status` option, equivalent to `-I` from `spack spec` * Shows install status for either `-c` or `-i` * As a side effect to prior point, `spack find -i` can now distinguish different installation states (upstream/external) Examples: ``` $ spack find -r ==> In environment findtest ==> 1 root specs - raja ==> 6 installed packages (not shown) ==> 12 concretized packages to be installed (not shown) ``` ``` $ spack find ==> In environment findtest ==> 1 root specs - raja -- darwin-ventura-m1 / apple-clang@14.0.3 ----------------------- berkeley-db@18.1.40 bzip2@1.0.8 diffutils@3.10 gmake@4.4.1 gnuconfig@2022-09-17 libiconv@1.17 ==> 6 installed packages ==> 12 concretized packages to be installed (show with `spack find -c`) ``` ``` $ spack find -c ==> In environment findtest ==> 1 root specs - raja -- darwin-ventura-m1 / apple-clang@14.0.3 ----------------------- [+] berkeley-db@18.1.40 [+] bzip2@1.0.8 - cmake@3.29.4 [+] diffutils@3.10 [+] gmake@4.4.1 [+] libiconv@1.17 - nghttp2@1.62.0 - pkgconf@2.2.0 - readline@8.2 - blt@0.6.2 - camp@2024.02.1 - curl@8.7.1 - gdbm@1.23 [+] gnuconfig@2022-09-17 - ncurses@6.5 - perl@5.38.2 - raja@2024.02.2 - zlib-ng@2.1.6 ==> 6 installed packages ==> 12 concretized packages to be installed ``` $ spack -E find ... ==> 82 installed packages ```
2024-07-06spack -C <env>: use env config w/o activation (#45046)Harmen Stoppels1-1/+1
Precedence: 1. Named environment 2. Anonymous environment 3. Generic directory
2024-07-04containers: rm centos7 since EOL (#45049)Wouter Deconinck1-28/+0
2024-07-03[openfoam]: use latest cgal (#45003)Robert Cohn1-1/+1
* [openfoam]: use latest cgal * add version checks for CGAL
2024-07-02Revert "e4s ci: reduce size due to 5mb gitlab artifact limit (#44986)" (#45001)Harmen Stoppels1-60/+60
This reverts commit 18de6a480b5c97c1a9bc08c3eaf82cfc63617ce3.
2024-07-02ci: deprecate the --dependencies and --optimize option (#45005)Massimiliano Culpo1-2/+2
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2025-01-04 11:02:37 +0000