summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2021-12-23Turn some verbose messages into debug messages (#27408)Harmen Stoppels1-8/+8
2021-12-23Fix overloaded argparse keys (#27379)Harmen Stoppels6-21/+15
Commands should not reuse option names defined in main.
2021-12-23Fix log-format reporter ignoring install errors (#25961)Jordan Galby3-31/+48
When running `spack install --log-format junit|cdash ...`, install errors were ignored. This made spack continue building dependents of failed install, ignoring `--fail-fast`, and exit 0 at the end.
2021-12-23openmpi fix external find for 0.17 (#27255)Robert Underwood1-1/+1
2021-12-23make --enable-locks actually enable locks (#24675)Dylan Simon1-2/+3
2021-11-13elfutils: add version 0.186 (#27345)Mark W. Krentel1-0/+1
2021-11-05Update CHANGELOG.md for 0.17.0v0.17.0Todd Gamblin1-0/+184
2021-11-05bump version number to 0.17.0Todd Gamblin2-2/+2
2021-11-05py-itk: fix dependencies (#27164)Ben Darwin1-3/+2
2021-11-05New package: GNDS (#27176)Seth R. Johnson1-0/+28
Adds a new package for the AMPX/SCALE implementation of the GNDS interface, https://www.oecd.org/publications/specifications-for-the-generalised-nuclear-database-structure-gnds-94d5e451-en.htm .
2021-11-05qt: replace conflicts('%gcc@11:', when='@5.9:5.14') with -include limits ↵Bernhard Kaindl1-2/+6
(#27241) Noting that missing numeric_limits was the cause of the compile issues with gcc-11, I tested adding -include limits fixing @5.9:5.14%gcc@11. Therefore, we can replace the conflicts('%gcc@11:', when='@5.9:5.14'). Co-authored-by: Bernhard Kaindl <bernhard.kaindl@ait.ac.at>
2021-11-05py-mpi4py: Add newer versions (#27239)Theofilos Manitaras1-2/+7
* py-mpi4py: Add newer versions * Address PR comments
2021-11-05openPMD-api: 0.14.3 (#27211)Axel Huebl1-0/+1
Add the latest release.
2021-11-05Prevent additional properties to be in the answer set when reusing specs ↵Massimiliano Culpo3-1/+42
(#27240) * Prevent additional properties to be in the answer set when reusing specs fixes #27237 The mechanism to reuse concrete specs relies on imposing the set of constraints stemming from the concrete spec being reused. We also need to prevent that other constraints get added to this set.
2021-11-05ctags uses custom autogen.sh script (#27229)Peter Brady1-0/+3
2021-11-05package/py-zarr_add_v2.10.2 (#27212)Sinan1-0/+2
* package/py-zarr_add_v2.10.2 * improve python dep version constraints Co-authored-by: sbulut <sbulut@3vgeomatics.com>
2021-11-05hdf5: Skip racy test cases(which loop endless on many cores) (#27068)Bernhard Kaindl1-0/+7
2021-11-05trilinos: explicitly use variants instead of spec for TPLs (#27221)Seth R. Johnson1-25/+34
Fixes https://github.com/spack/spack/pull/27188#issuecomment-961212214
2021-11-05r-readr: add 2.0.2 (#27177)Manuela Kuhn1-3/+8
2021-11-05exaworks: swift-t package (#27234)Mikhail Titov1-2/+1
2021-11-05gmsh: add dependency on gl and glu providers when +fltk (#27169)Carlos Bederián1-1/+2
2021-11-05make version docs reflect reality (#27149)Harmen Stoppels1-26/+30
* make version docs reflect reality * typo and make things * 2.6 -> 2.7 in example
2021-11-05hpx: simplify instrumentation_args function (#27226)Massimiliano Culpo1-7/+4
2021-11-05commands: `spack load --list` alias for `spack find --loaded` (#27184)Todd Gamblin10-11/+64
See #25249 and https://github.com/spack/spack/pull/27159#issuecomment-958163679. This adds `spack load --list` as an alias for `spack find --loaded`. The new command is not as powerful as `spack find --loaded`, as you can't combine it with all the queries or formats that `spack find` provides. However, it is more intuitively located in the command structure in that it appears in the output of `spack load --help`. The idea here is that people can use `spack load --list` for simple stuff but fall back to `spack find --loaded` if they need more. - add help to `spack load --list` that references `spack find` - factor some parts of `spack find` out to be called from `spack load` - add shell tests - update docs Co-authored-by: Peter Josef Scheibel <scheibel1@llnl.gov> Co-authored-by: Richarda Butler <39577672+RikkiButler20@users.noreply.github.com>
2021-11-05spfft: add version 1.0.5 (#27223)Simon Frasch1-0/+3
2021-11-05spla: add version 1.5.2 (#27222)Simon Frasch1-0/+3
2021-11-05docs for experimental `--reuse` argument to `spack install`Todd Gamblin1-0/+28
Add docs for `--reuse`, along with a warning that it will likely be removed and refactored.
2021-11-05error message for reusing multiple hashes for packageGregory Becker1-1/+2
2021-11-05concretizer: add error messages and simplify asp.pyTodd Gamblin2-8/+18
2021-11-05Fix logic program for multi-valued variantsMassimiliano Culpo1-45/+71
Reformulate variant rules so that we minimize both 1. The number of non-default values being used 2. The number of default values not-being used This is crucial for MV variants where we may have more than one default value
2021-11-05bugfix: handle hashes that only exist in input specsTodd Gamblin1-27/+48
In our tests, we use concrete specs generated from mock packages, which *only* occur as inputs to the solver. This fixes two problems: 1. We weren't previously adding facts to encode the necessary `depends_on()` relationships, and specs were unsatisfiable on reachability. 2. Our hash lookup for reconstructing the DAG does not consider that a hash may have come from the inputs.
2021-11-05concretizer: exempt already-installed specs from compiler and variant rulesTodd Gamblin2-7/+22
Concrete specs that are already installed or that come from a buildcache may have compilers and variant settings that we do not recognize, but that shouldn't prevent reuse (at least not until we have a more detailed compiler model). - [x] make sure compiler and variant consistency rules only apply to built specs - [x] don't validate concrete specs on input, either -- they're concrete and we shouldn't apply today's rules to yesterday's build
2021-11-05spack diff: more flexible tests, restore transitive diff with spec_clausesTodd Gamblin3-12/+39
In switching to hash facts for concrete specs, we lost the transitive facts from dependencies. This was fine for solves, because they were implied by the imposed constraints from every hash. However, for `spack diff`, we want to see what the hashes mean, so we need another mode for `spec_clauses()` to show that. This adds a `expand_hashes` argument to `spec_clauses()` that allows us to output *both* the hashes and their implications on dependencies. We use this mode in `spack diff`.
2021-11-05Add a missing definition in the logic programMassimiliano Culpo1-0/+1
2021-11-05Add buildcache to reusable specsMassimiliano Culpo4-16/+51
2021-11-05spack install: add --reuse argumentMassimiliano Culpo3-5/+7
2021-11-05spack concretize: add --reuse argumentMassimiliano Culpo5-17/+36
2021-11-05spack spec: add --reuse argumentMassimiliano Culpo5-18/+35
2021-11-05concretizer: get rid of last maximize directive in concretize.lpTodd Gamblin1-32/+5
- [x] Get rid of forgotten maximize directive. - [x] Simplify variant handling - [x] Fix bug in treatment of defaults on externals (don't count non-default variants on externals against them)
2021-11-05Update command completionMassimiliano Culpo1-1/+1
2021-11-05Trim dependencies on externalsMassimiliano Culpo1-1/+2
2021-11-05Fix a unit test to match the new OS semanticsMassimiliano Culpo1-1/+1
CNL, debian6 and Suse are not compatible
2021-11-05ASP-based solve: if an OS is set, respect the valueMassimiliano Culpo1-0/+3
2021-11-05Fix a type in "variant_not_default" ruleMassimiliano Culpo1-1/+1
2021-11-05concretizer: rework spack solve output to handle reuse betterTodd Gamblin3-75/+137
2021-11-05spec: ensure_valid_variants() should not validate concrete specsTodd Gamblin1-0/+4
Variants in concrete specs are "always" correct -- or at least we assume them to be b/c they were concretized before. Their variants need not match the current version of the package.
2021-11-05concretizer: unify handling of single- and multi-valued variantsTodd Gamblin1-18/+5
Multi-valued variants previously maximized default values to handle cases where the default contained two values, e.g.: variant("foo", default="bar,baz") This is because previously we were minimizing non-default values, and `foo=bar`, `foo=baz`, and `foo=bar,baz` all had the same score, as none of them had any "non-default" values. This commit changes the approach and considers a non-default value to be either a value set to something not default *or* the absence of a default value from the set value. This allows multi- and single-valued variants to be handled the same way, with the same minimization criterion. It alse means that the "best" value for every optimization criterion is now zero, which allows us to make useful assumptions about the optimization criteria.
2021-11-05concretizer: reuse installs, but assign default values for new buildsTodd Gamblin1-35/+119
Minimizing builds is tricky. We want a minimizing criterion because we want to reuse the avaialble installs, but we also want things that have to be built to stick to *default preferences* from the package and from the user. We therefore treat built specs differently and apply a different set of optimization criteria to them. Spack's *first* priority is to reuse what it can, but if it builds something, the built specs will respect defaults and preferences. This is implemented by bumping the priority of optimization criteria for built specs -- so that they take precedence over the otherwise topmost-priority criterion to reuse what is installed. The scheme relies on all of our optimization criteria being minimizations. That is, we need the case where all specs are reused to be better than any built spec could be. Basically, if nothing is built, all the build criteria are zero (the best possible) and the number of built packages dominates. If something *has* to be built, it must be strictly worse than full reuse, because: 1. it increases the number of built specs 2. it must have either zero or some positive number for all criteria Our optimziation criteria effectively sum into two buckets at once to accomplish this. We use a `build_priority()` number to shift the priority of optimization criteria for built specs higher.
2021-11-05tests: make `spack diff` test more lenientTodd Gamblin1-4/+12
The constraints in the `spack diff` test were very specific and assumed a lot about the structure of what was being diffed. Relax them a bit to make them more resilient to changes.
2021-11-05concretizer: only minimize builds when `--reuse` is enabled.Todd Gamblin2-1/+4
Make the first minimization conditional on whether `--reuse` is enabled in the solve. If `--reuse` is not enabled, there will be nothing in the set to minimize and the objective function (for this criterion) will be 0 for every answer set.