summaryrefslogtreecommitdiff
path: root/lib
AgeCommit message (Collapse)AuthorFilesLines
2023-06-05Update RtD and Sphinx configuration (#38046)Massimiliano Culpo3-42/+29
2023-06-01Memoize a few hot functions during module file generation (#37739)Massimiliano Culpo5-13/+16
2023-06-01Spec.format: print false attributes if requested (#37932)Greg Becker2-1/+2
2023-05-31CachedCMakePackage: add CUDA/HIP options and improve independent builds (#37592)Brian Van Essen1-9/+83
* Add CMake options for building with CUDA/HIP support to CachedCMakePackages (intended to reduce duplication across packages building with +hip/+cuda and using CachedCMakePackage) * Define generic variables like CMAKE_PREFIX_PATH for CachedCMakePackages (so that a user may invoke "cmake" themselves without needing to setthem on the command line). * Make `lbann` a CachedCMakePackage. Co-authored-by: Chris White <white238@llnl.gov>
2023-05-30Bugfix: cray manifest parsing regression (#37909)Tiziano Müller3-4/+18
fa7719a changed syntax for specifying exact versions, which are required for some compiler specs (including those read as part of parsing a Cray manifest). This fixes that and also makes a couple other improvements to manifest parsing. * Instantiate compiler specs with exact versions (fixes #37893) * fix slingshot network detection (CPE 22.10+ has libcxi.so in /usr/lib64) * "spack external find": add arg to ignore default dir for cray manifests
2023-05-30Simplify implementation of "get_compiler_config" (#37989)Massimiliano Culpo1-28/+18
2023-05-29Remove patchelf self-relocation (#33834)Harmen Stoppels2-43/+1
2023-05-29fix InternalConcretizerError msg (#37791)Harmen Stoppels1-6/+7
2023-05-29Bugfix/tests: add slash to test log message (#37874)Tamara Dahlgren1-1/+1
2023-05-29tests/sip: convert to new stand-alone test process (#35693)Tamara Dahlgren1-7/+10
2023-05-28modules: improve default naming scheme (#37808)Xavier Delaruelle4-38/+38
Change default naming scheme for tcl modules for a more user-friendly experience. Change from flat projection to "per software name" projection. Flat naming scheme restrains module selection capabilities. The `{name}/{version}...` scheme make possible to use user-friendly mechanisms: * implicit defaults (`module load git`) * extended default (`module load git/2`) * advanced version specifiers (`module load git@2:`)
2023-05-26CI: Use relative path in default script (#36649)kwryankrattiger1-1/+1
2023-05-25Windows MSVC: do not set sdk version if installing sdk (#37930)John W. Parent1-1/+5
Note the win-sdk package is not installable and reports an error which instructs the user how to add it. Without this fix, a (more confusing) error occurs before this message can be generated.
2023-05-25Windows: fix "spack build-env" (#37923)John W. Parent3-3/+21
"spack build-env" was not generating proper environment variable definitions on Windows; this commit updates the generated commands to succeed with batch/PowerShell.
2023-05-25Bugfix/tests: write not append stand-alone test status (#37841)Tamara Dahlgren2-1/+26
2023-05-24bugfix: env concretize after remove (#37877)Greg Becker2-0/+27
2023-05-24spack remove: fix traversal when user specs intersect (#37882)Harmen Stoppels1-21/+20
drop unnecessary double loop over the matching user specs.
2023-05-23Remove myself as maintainer of R packages (#37859)Glenn Johnson1-3/+1
* Remove myself as maintainer of R packages I will no longer have the time to properly maintain these packages. * fix flake8 test for import
2023-05-22deleted package.py better error message (#37814)simonleary-umass-edu1-1/+1
adds the namespace to the exception object's string representation
2023-05-19spack env create: generate a view when newly created env has concrete specs ↵Harmen Stoppels2-1/+23
(#37799)
2023-05-19archspec: fix entry in the JSON file (#37793)Massimiliano Culpo2-2/+2
2023-05-19lmod: allow core compiler to be specified with a version range (#37789)Massimiliano Culpo5-22/+48
Use CompilerSpec with satisfies instead of string equality tests Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>
2023-05-19compiler specs: do not print '@=' when clear from context (#37787)Greg Becker4-12/+22
Ensure that spack compiler add/find/list and lists of concrete specs print the compiler effectively as {compiler.name}{@compiler.version}. Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>
2023-05-18Remove references to gmake executable, only use make (#37280)Dom Heinzeller2-2/+0
2023-05-18Bump Spack version on develop to 0.21.0.dev0 (#37760)Massimiliano Culpo1-1/+1
2023-05-18Bugfix: allow preferred new versions from externals (#37747)Peter Scheibel2-92/+126
2023-05-17maintainers: switch from list to directive (#37752)Tamara Dahlgren4-1195/+1284
2023-05-17Limit deepcopy to just the initial "all" section (#37718)Massimiliano Culpo1-12/+7
Modifications: - [x] Limit the scope of the deepcopy when initializing module file writers
2023-05-17gitlab ci: no copy-only pipelines w/ deprecated config (#37720)Scott Wittenburg1-6/+22
Make it clear that copy-only pipelines are not supported while still using the deprecated ci config format. Also ensure that the deprecated stack does not fail on spack pipelines for tags.
2023-05-17spack test: fix stand-alone test suite status reporting (#37602)Tamara Dahlgren4-40/+187
* Fix reporting of packageless specs as having no tests * Add test_test_output_multiple_specs with update to simple-standalone-test (and tests) * Refactored test status summary; added more tests or checks
2023-05-17Add recently added Spack Docker Images to documentation (#37732)Yoshiaki Senda1-0/+20
Signed-off-by: Yoshiaki Senda <yoshiaki@live.it>
2023-05-17Fix `spack find` not able to display version ranges in compilers (#37715)Massimiliano Culpo2-1/+16
2023-05-16Windows: fix MSVC version handling (#37711)John W. Parent1-2/+2
MSVC compiler logic was using string parsing to extract version from compiler spec, which was fragile. This broke in #37572, so has been fixed and made more robust by using attribute access.
2023-05-16Requirements and preferences should not define (non-git) versions (#37687)Peter Scheibel4-9/+174
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-16check_modules_set_name: do not check for "enable" key (#37701)Harmen Stoppels2-14/+46
2023-05-16unify: when_possible and unify: true -- Bugfix for error in 37438 (#37681)Greg Becker1-6/+15
Two bugs came in from #37438 1. `unify: when_possible` was broken, because of an incorrect assertion. abstract/concrete spec pairs were compared against the results that were in the process of being computed, rather than against the previous results. 2. `unify: true` had an ordering bug that could mix the association between abstract and concrete specs - [x] 1 is resolved by creating a lookup from old concrete specs to old abstract specs, and we use that to associate the "new" concrete specs that happen to be the old ones with their abstract specs (since those are stripped out for concretization - [x] 2 is resolved by combining the new and old abstract as lists instead of combining them as sets. This is important because `set() | set()` does not make any ordering promises, even though set ordering is otherwise guaranteed in `python@3.7:`
2023-05-15Improve package source code context display on error (#37655)Carson Woods2-12/+22
Spack displays package code context when it shouldn't (e.g., on `FetchError`s) and doesn't display it when it should (e.g., when errors occur in builder classes. The line attribution can sometimes be off by one, as well. - [x] Display package context when errors occur in a subclass of `PackageBase` - [x] Display package context when errors occur in a subclass of `BaseBuilder` - [x] Do not display package context when errors occur in `PackageBase`, `BaseBuilder` or other core code that is not in a `package.py` file. - [x] Fix off-by-one error for core code (don't subtract one from the line number *unless* it's in an actual `package.py` file. --------- Co-authored-by: Todd Gamblin <tgamblin@llnl.gov>
2023-05-15bugfix: allow reuse of packages from foreign namespacesTodd Gamblin1-5/+19
We currently throw a nasty error if you try to reuse packages from some other namespace (e.g., OLCF), but we should be able to reuse patched local versions of builtin packages. Right now the only obstacle to that is that we try to look up virtual info for unknown namespaces, and we can't get the package from the repo to do that. We *can* assume that a package with a known namespace is similar, and that its virtual provider information is reasonably accurate, so we now do that. This isn't 100% accurate, but neither is relying on the package itself, as it may have gone out of date. The real solution here is virtual edge information, but this is a stopgap until we have that.
2023-05-15bugfix: don't look up virtual information for unknown packagesTodd Gamblin1-3/+14
`spec_clauses()` attempts to look up package information for concrete specs in order to determine which virtuals they may provide. This fails for renamed/deleted dependencies of buildcaches and installed packages. This will eventually be fixed by #35258, which adds virtual information on edges, but we need a workaround to make older buildcaches usable. - [x] make an exception for renamed packages and omit their virtual constraints - [x] add a note that this will be solved by adding virtuals to edges
2023-05-15bugfix: don't look up patches from packages for concrete specsTodd Gamblin1-3/+3
The concretizer can fail with `reuse:true` if a buildcache or installation contains a package with a dependency that has been renamed or deleted in the main repo (e.g., `netcdf` was refactored to `netcdf-c`, `netcdf-fortran`, etc., but there are still binary packages with dependencies called `netcdf`). We should still be able to install things for which we are missing `package.py` files. `Spec.inject_patches_variant()` was failing this requirement by attempting to look up the package class for concrete specs. This isn't needed -- we can skip it. - [x] swap two conditions in `Spec.inject_patches_variant()`
2023-05-15Bump tutorial command (#37674)Harmen Stoppels1-1/+1
2023-05-15`spack find`: get rid of @= in arch/compiler headers (#37672)Todd Gamblin1-1/+1
The @= in `spack find` output adds a bit of noise. Remove it as we did for `spack spec` and `spack concretize`. This modifies display_specs so it actually covers other places we use that routine, as well, e.g., `spack buildcache list`. before: ``` -- linux-ubuntu20.04-aarch64 / gcc@=11.1.0 ----------------------- ofdlcpi libpressio@0.88.0 ``` after: ``` -- linux-ubuntu20.04-aarch64 / gcc@11.1.0 ----------------------- ofdlcpi libpressio@0.88.0 ```
2023-05-14concretizer: don't change concrete environments without `--force` (#37438)Greg Becker3-32/+71
If a user does not explicitly `--force` the concretization of an entire environment, Spack will try to reuse the concrete specs that are already in the lockfile. --------- Co-authored-by: becker33 <becker33@users.noreply.github.com> Co-authored-by: Todd Gamblin <tgamblin@llnl.gov>
2023-05-13`spack spec`: remove noisy `@=` from output (#37663)Todd Gamblin5-21/+39
@= is accurate, but noisy. Other UI commands tend not to print the redundant `@=` for known concrete versions; make `spack spec` consistent with them.
2023-05-12gitlab ci: release fixes and improvements (#37601)Scott Wittenburg2-4/+21
* 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-12Allow buildcache specs to be referenced by hash (#35042)Nathan Hanford8-93/+256
Currently, specs on buildcache mirrors must be referenced by their full description. This PR allows buildcache specs to be referenced by their hashes, rather than their full description. ### How it works Hash resolution has been moved from `SpecParser` into `Spec`, and now includes the ability to execute a `BinaryCacheQuery` after checking the local store, but before concluding that the hash doesn't exist. ### Side-effects of Proposed Changes Failures will take longer when nonexistent hashes are parsed, as mirrors will now be scanned. ### Other Changes - `BinaryCacheIndex.update` has been modified to fail appropriately only when mirrors have been configured. - Tests of hash failures have been updated to use `mutable_empty_config` so they don't needlessly search mirrors. - Documentation has been clarified for `BinaryCacheQuery`, and more documentation has been added to the hash resolution functions added to `Spec`.
2023-05-12Update archspec to v0.2.1 (#37633)Massimiliano Culpo2-4/+14
2023-05-12Fix logic in setting oneapi microarchitecture flags (#37634)Robert Cohn1-2/+4
2023-05-12Improve error message for buildcaches (#37626)Massimiliano Culpo2-6/+23
2023-05-12Improve error messages when Spack finds a too new DB / lockfile (#37614)Massimiliano Culpo4-10/+56
This PR ensures that we'll get a comprehensible error message whenever an old version of Spack tries to use a DB or a lockfile that is "too new". * Fix error message when using a too new DB * Add a unit-test to ensure we have a comprehensible error message