summaryrefslogtreecommitdiff
path: root/share
AgeCommit message (Collapse)AuthorFilesLines
2023-05-25update ci ml darwin keypath (#37927)eugeneswalker1-3/+3
2023-05-25Add macOS ML CI stacks (#36586)Adam J. Stewart6-172/+223
* Add macOS ML CI stacks * torchmeta is no longer maintained and requires ancient PyTorch * Add MXNet * update darwin aarch64 stacks * add darwin-aarch64 scoped config.yaml * remove unnecessary cleanup job * fix specifications * fix labels * fix labels * fix indent on tags specification * no tags for trigger jobs * try overriding tags in stack spack.yaml * do not use CI_STACK_CONFIG_SCOPES * incorporate config:install_tree:root: overrides and compiler defs * copy relevant ci-scoped config settings directly into stack spack.yaml * remove build-job-remove * spack ci generate: add debug flag * include cdash config directly in stack spack.yaml * customize build-job script section to avoid absolute paths * add any-job specification * tags: use aarch64-macos instead of aarch64 * generate tags: use aarch64-macos instead of aarch64 * do not add morepadding * use shared mirror; comment out known failures * remove any-job * nproc || true * comment out specs failing due to bazel from cache codesign issue --------- Co-authored-by: eugeneswalker <eugenesunsetwalker@gmail.com>
2023-05-24Pcluster local buildcache (#37852)Stephen Sachs5-38/+23
* [pcluster pipeline] Use local buildcache instead of upstream spack Spack currently does not relocate compiler references from upstream spack installations. When using a buildcache we don't need an upstream spack. * gcc needs to be installed via postinstall to get correct deps * quantum-espresso@gcc@12.3.0 returns ICE on neoverse_{n,v}1 * Force gitlab to pull the new container * Revert "Force gitlab to pull the new container" This reverts commit 3af5f4cd88245138992deb2a46c17e6f85858d68. Seems the gitlab version does not yet support "pull_policy" in .gitlab-ci.yml * Gitlab keeps picking up wrong container. Renaming * Update containers once more after failed build
2023-05-23e4s ci: add dealii (#32484)eugeneswalker1-0/+1
2023-05-17Add aws-plcuster[-aarch64] stacks (#37627)Stephen Sachs9-0/+394
Add aws-plcuster[-aarch64] stacks. These stacks build packages defined in https://github.com/spack/spack-configs/tree/main/AWS/parallelcluster They use a custom container from https://github.com/spack/gitlab-runners which includes necessary ParallelCluster software to link and build as well as an upstream spack installation with current GCC and dependencies. Intel and ARM software is installed and used during the build stage but removed from the buildcache before the signing stage. Files `configs/linux/{arch}/ci.yaml` select the necessary providers in order to build for specific architectures (icelake, skylake, neoverse_{n,v}1).
2023-05-16CI: Expand E4S ROCm stack to include missing DaV packages (#36843)kwryankrattiger1-3/+3
* CI: Expand E4S ROCm stack to include missing DaV packages Ascent: Fixup for VTK-m with Kokkos backend * DaV SDK: Removed duplicated openmp variant for ascent * Drop visit and add conflict for Kokkos * E4S: Drop ascent from CUDA builds
2023-05-16Requirements and preferences should not define (non-git) versions (#37687)Peter Scheibel1-2/+2
Ensure that requirements `packages:*:require:@x` and preferences `packages:*:version:[x]` fail concretization when no version defined in the package satisfies `x`. This always holds except for git versions -- they are defined on the fly.
2023-05-16gitlab ci: reduce job name length of build_systems pipeline (#37686)Scott Wittenburg1-1/+1
2023-05-15oneapi: before script load modules (#37678)Harmen Stoppels1-0/+4
2023-05-13e4s ci stacks: add: hdf5-vol-{log,cache} (#37651)eugeneswalker2-0/+4
2023-05-12gitlab ci: release fixes and improvements (#37601)Scott Wittenburg2-460/+197
* gitlab ci: release fixes and improvements - use rules to reduce boilerplate in .gitlab-ci.yml - support copy-only pipeline jobs - make pipelines for release branches rebuild everything - make pipelines for protected tags copy-only * gitlab ci: remove url changes used in testing * gitlab ci: tag mirrors need public key Make sure that mirrors associated with release branches and tags contain the public key needed to verify the signed binaries. This also ensures that when stack-specific mirror contents are copied to the root, the root mirror has the public key as well. * review: be more specific about tags, curl flags * Make the check in ci.yaml consistent with the .gitlab-ci.yml --------- Co-authored-by: Ryan Krattiger <ryan.krattiger@kitware.com>
2023-05-11e4s ci: trilinos +rocm: enable belos to fix build failure (#37617)eugeneswalker1-1/+1
2023-05-11Allow using -j to control the parallelism of concretization (#37608)Massimiliano Culpo1-1/+1
fixes #29464 This PR allows to use ``` $ spack concretize -j X ``` to set a cap on the parallelism of concretization from the command line
2023-05-10ci: remove --mirror-url flag (#37457)Harmen Stoppels1-1/+1
The flags --mirror-name / --mirror-url / --directory were deprecated in favor of just passing a positional name, url or directory, and letting spack figure it out. --------- Co-authored-by: Scott Wittenburg <scott.wittenburg@kitware.com>
2023-05-10New option "--first" for "spack location" (#36283)G-Ragghianti1-2/+2
2023-05-08use latest trilinos for +cuda variants (#37164)eugeneswalker2-4/+4
2023-05-07gitlab ci: bump tutorial image (#37544)Harmen Stoppels2-3/+3
2023-05-05Add spack buildcache push (alias to buildcache create) (#34861)Harmen Stoppels1-2/+20
`spack buildcache create` is a misnomer cause it's the only way to push to an existing buildcache (and it in fact calls binary_distribution.push). Also we have `spack buildcache update-index` but for create the flag is `--rebuild-index`, which is confusing (and also... why "rebuild" something if the command is "create" in the first place, that implies it wasn't there to begin with). So, after this PR, you can use either ``` spack buildcache create --rebuild-index ``` or ``` spack buildcache push --update-index ``` Also, alias `spack buildcache rebuild-index` to `spack buildcache update-index`.
2023-05-05Update tutorial pipeline to Ubuntu 22.04 (#35451)Harmen Stoppels2-9/+11
2023-05-05ci: stop downloading recent gmake (#37458)Harmen Stoppels3-13/+0
2023-05-04Allow choosing the name of the packages subdirectory in repositories (#36643)Greg Becker1-1/+1
Co-authored-by: becker33 <becker33@users.noreply.github.com>
2023-04-28Add container images supporting RHEL alternatives (#36713)Jonathon Anderson6-0/+176
Add container support for AlmaLinux, Fedora 37 and 38 and Rocky Linux
2023-04-24e4s ci: add xyce (#36841)eugeneswalker2-8/+20
* e4s ci: add xyce * relax trilinos contraints for xyce * also relax trilinos constraint for e4s-power stack * allow trilinos~shylu for xyce
2023-04-24e4s ci: add mgard (#36584)eugeneswalker2-0/+4
2023-04-24MXNet: add v1.9 (#36590)Adam J. Stewart3-0/+9
2023-04-21Hraden Spack's powershell interface (#37079)John W. Parent2-3/+2
Paths with spaces are an issue on Windows and our current powershell scripts are not sufficiently hardended against their use. This PR removes promlematic commandlets that do not work well with paths with spaces and adds escape quotes in other areas where this could be an issue.
2023-04-20ML CI: fix mirror name (#37007)Adam J. Stewart2-2/+2
2023-04-18DaV SDK: Enable ParaView raytracing with in SDK (#36844)kwryankrattiger1-1/+7
* DaV SDK: Enable ParaView raytracing with in SDK * CI: Drop swr testing from Data Vis SDK * ISPC: extend LLVM requirement to main * DaV SDK: Disallow concretizing develop unifyfs No longer needed after mochi-margo patch
2023-04-17CI: update Linux images in ML pipelines (#36766)Adam J. Stewart4-12/+18
Add missing openssl/curl/pkgconfig deps to py-tokenizers Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>
2023-04-14gitlab ci: Better tagging of "service" jobs (#36846)Scott Wittenburg1-0/+21
- Tag non-rebuild jobs to target a cheaper (and more highly available) subset of runners. - Add missing resource requests to these jobs as well.
2023-04-13remove x86_64_v3 tags (#36828)eugeneswalker1-4/+4
2023-04-13containerize: strip binaries in a less aggressive way (#36683)Massimiliano Culpo2-2/+2
2023-04-13CI: Update Data Vis SDK image (#36761)kwryankrattiger2-3/+3
Supersedes #34224
2023-04-10ci: gpu-tests stack: swap x86_64-{cuda,rocm} for x86_64 (#36759)eugeneswalker1-2/+6
2023-04-10Ci backwards compat (#36045)kwryankrattiger2-0/+167
* CI: Fixup docs for bootstrap. * CI: Add compatibility shim * Add an update method for CI Update requires manually renaming section to `ci`. After this patch, updating and using the deprecated `gitlab-ci` section should be possible. * Fix typos in generate warnings * Fixup CI schema validation * Add unit tests for legacy CI * Add deprecated CI stack for continuous testing * Allow updating gitlab-ci section directly with env update * Make warning give good advice for updating gitlab-ci * Fix typo in CI name * Remove white space * Remove unneeded component of deprected-ci
2023-04-06Ecp hdf5 vol (#35195)kwryankrattiger1-0/+1
* ECP-SDK: enable hdf5 VOL adapters - When +hdf5, enable VOL adapters suitable for the SDK. - Each VOL package must prepend to the HDF5_PLUGIN_PATH. - hdf5: 1.13.3 will break existing VOL packages, constrain VOLs related to SDK and add note to keep 1.13.2 available. - hdf5-vol-async: - Do not set HDF5_VOL_CONNECTOR, consumers must opt-in. - Enforce DAG constraints on MPI to require threaded version. - Depend on an explicit version of argbots to relax concretization issues in other spack environments. - paraview: fix compiler flag usage for the 110 ABI (followup to #33617). * ECP Data and ViS: Add constraits for HDF5 VOLS * CI: HDF5 1.14 builds without VisIt * hdf5-vol-async: Update docs string --------- Co-authored-by: Stephen McDowell <stephen.mcdowell@kitware.com>
2023-04-03Improve Dockerfile recipe generation (#35187)Massimiliano Culpo2-4/+21
- Update default image to Ubuntu 22.04 (previously was still Ubuntu 18.04) - Optionally use depfiles to install the environment within the container - Allow extending Dockerfile Jinja2 template - Allow extending Singularity definition file Jinja2 template - Deprecate previous options to add extra instructions
2023-03-31gitlab ci: request more memory for publish job (#36560)Scott Wittenburg1-0/+2
2023-03-29ci: require x86_64_v3 everywhere (#36158)Harmen Stoppels13-241/+211
2023-03-28e4s power ci: ecp-data-vis-sdk: disable visit due to build issues (#36475)eugeneswalker1-1/+1
2023-03-27modules: enhance help message (#36410)Xavier Delaruelle2-3/+11
Update tcl and lmod modulefile template to provide more information on help message (name, version and target) like done on whatis for lmod modulefiles.
2023-03-24modules: add support for append_flags/remove_flags (#36402)Xavier Delaruelle2-4/+4
Adapt tcl and lmod modulefile templates to generate append-path or remove-path commands in modulefile when respectively append_flags or remove_flags commands are defined in package for run environment. Fixes #10299.
2023-03-24modules tcl: simplify env modification block in template (#36334)Xavier Delaruelle1-16/+0
Simplify environment modification block in modulefile Tcl template by always setting a path delimiter to the prepend-path, append-path and remove-path commands. Remove --delim option to the setenv command as this command does not allow such option. Update test_prepend_path_separator test to explicitly check the 6 path-like commands that should be present in generated modulefile.
2023-03-20spack install: simplify behavior when inside environments (#35206)Harmen Stoppels1-2/+2
Example one: ``` spack install --add x y z ``` is equivalent to ``` spack add x y z spack concretize spack install --only-concrete ``` where `--only-concrete` installs without modifying spack.yaml/spack.lock Example two: ``` spack install ``` concretizes current spack.yaml if outdated and installs all specs. Example three: ``` spack install x y z ``` concretizes current spack.yaml if outdated and installs *only* concrete specs in the environment that match abstract specs `x`, `y`, or `z`.
2023-03-20modules tcl: fix autoload mechanism in template (#36237)Xavier Delaruelle1-6/+1
Adapt tcl modulefile template to call "module load" on autoload dependency without testing if this dependency is already loaded or not. The is-loaded test is not necessary, as module commands know how to cope with an already loaded module. With environment-modules 4.2+ (released in 2018) it is also important to have this "module load" command even if dependency is already loaded in order to record that the modulefile declares such dependency. This is important if you want to keep a consistent environment when a dependent module is unloaded. The "Autoloading" verbose message is also removed as recent module commands will report such information to the user (depending on the verbosity configured for the module command). Such change has been test successfully with Modules 3.2 (EL7), 4.5 (EL8) and 5.2 (latest) and also with Lmod 7 and 8 (as it is mentionned in Spack docs that Lmod can be used along with tcl modules). Dependencies are correctly loaded or unloaded, whether they are loaded/unloaded or not. This change fixes Tcl quoting issue introduced in #32853. Fixes #19155.
2023-03-19Fix case spelling for Lmod and Tcl (#36215)Xavier Delaruelle2-2/+2
2023-03-17Update the PyTorch ecosystem (#36132)Adam J. Stewart3-0/+3
* py-pytorch-lightning: add v2.0.0 * py-lightning-utilities: add v0.8.0 * Update all PyTorch packages * Open-CE does not yet have patches for PyTorch 2 on ppc64le
2023-03-15Hotfix: CI: Add CI target for gpu-test stack (#36136)kwryankrattiger1-0/+1
2023-03-14Fix typo affecting Gitlab CI (#36103)Harmen Stoppels1-1/+1
Introduced in #35944
2023-03-14concretizer: add mode to reuse dependencies only (#30990)Michael Kuhn1-9/+9
This adds a new mode for `concretizer:reuse` called `dependencies`, which only reuses dependencies. Currently, `spack install foo` will reuse older versions of `foo`, which might be surprising to users.
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-16 10:22:50 +0000