- Jul 04, 2024
-
-
Eleni Mathioulaki authored
This reverts commit b5538960, which caused the concretization of some environments to hang indefinitely.
-
- Apr 15, 2024
-
-
Eleni Mathioulaki authored
Spack's spec hashing mechanism considers only build, link, and run dependencies, overlooking test dependencies. As a result, although Spack correctly concretizes environments when `--test root` is specified (including test dependencies), the resulting lockfile dict only includes the deps whose types affect the hash (build/link/run) and when the env is loaded, test dependencies are not, and tests fail. The workaround suggested in the Spack issue [here](https://github.com/spack/spack/issues/29447) is deleting the lockfile every time and allowing `spack install --test root` to recreate it. By extending Spack's default hash type to include test dependencies, the need for this workaround is eliminated and concretization and installation can be split into separate steps.
-
- Jan 12, 2024
-
-
Massimiliano Culpo authored
-
eugeneswalker authored
-
- Jan 11, 2024
-
-
Harmen Stoppels authored
Add forward compatibility for tarballs created by Spack 0.22, which use build cache layout version 2. Spack 0.21 continues to produce build cache layout version 1 tarballs. Build cache layout version 2 also lists parent directories of the package prefix in the tarball, which is required for certain container runtimes.
-
Harmen Stoppels authored
-
Harmen Stoppels authored
-
Harmen Stoppels authored
This fixes an issue where pkg.stage throws because a patch cannot be found, but the patch is redundant because the spec is reused from a build cache and will be installed from existing binaries.
-
Miguel Dias Costa authored
* update url for BerkeleyGW version 3.0.1 * update source urls and add version 3.1.0 to berkeleygw package
-
Harmen Stoppels authored
-
Massimiliano Culpo authored
This commit discards type mismatches or failures to validate a package preference during concretization. The values discarded are logged as debug level messages. It also adds a config audit to help users spot misconfigurations in packages.yaml preferences.
-
Massimiliano Culpo authored
-
Massimiliano Culpo authored
* solver: use a unique counter for condition, triggers and effects * Do not reset counters when re-running setup What we need is just a unique ID, it doesn't need to start from zero every time.
-
Todd Gamblin authored
This was missed while backporting the new `spack info` command from #40326. Variants should be sorted by name when invoking `spack info --variants-by-name`.
-
Stephen Sachs authored
-
Harmen Stoppels authored
-
Massimiliano Culpo authored
Co-authored-by: Harmen Stoppels <me@harmenstoppels.nl>
-
Harmen Stoppels authored
-
Harmen Stoppels authored
-
Harmen Stoppels authored
* tests: default_config drop scope * use default_config elsewhere * use parse_install_tree for missing defaults in default config
-
Harmen Stoppels authored
-
Harmen Stoppels authored
-
Harmen Stoppels authored
-
Harmen Stoppels authored
Can also be an environment root, or programatically `Spec("x").concretized()`.
-
Juan Miguel Carceller authored
Co-authored-by: jmcarcell <jmcarcell@users.noreply.github.com>
-
Dave Keeshan authored
Fix filer_compiler_wrapper for cases where the compiler returned in None, this happens on some installed gcc systems that do not have fortran built into them as standard, e.g. gcc@11.4.0 on ubuntu 22.04
-
- Jan 10, 2024
-
-
Robert Cohn authored
-
Michael Kuhn authored
PR #40929 reverted the argument parsing to make `spack --verbose install` work again. It looks like `--verbose` is the only instance where this kind of argument inheritance is used since all other commands override arguments with the same name instead. For instance, `spack --bootstrap clean` does not invoke `spack clean --bootstrap`. Therefore, fix multi-line aliases again by parsing the resolved arguments and instead explicitly pass down `args.verbose` to commands.
-
Massimiliano Culpo authored
If we use all specs, we won't color correctly build-only dependencies
-
John W. Parent authored
Co-authored-by: Harmen Stoppels <harmenstoppels@gmail.com>
-
Harmen Stoppels authored
This roughly restores the order of operation from Spack 0.20, where where `AutotoolsPackage.setup_build_environment` would override the env variable set in `setup_platform_environment` on macOS.
-
Massimiliano Culpo authored
When improving the error message, we started #showing in the answer set a lot more symbols - but we forgot to suppress the debug messages warning about UNKNOWN SYMBOLs
-
Harmen Stoppels authored
-
Harmen Stoppels authored
-
Massimiliano Culpo authored
Improves the warning for deprecated preferences, and adds a configuration audit to get files:lines details of the issues. Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
-
Massimiliano Culpo authored
* Add audit check to spot when= arguments using named specs * Fix package issues caught by the new audit
-
Harmen Stoppels authored
-
Massimiliano Culpo authored
-
Harmen Stoppels authored
-
- Nov 11, 2023
-
-
Todd Gamblin authored
Co-authored-by: Harmen Stoppels <me@harmenstoppels.nl>
-