summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
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.
2021-11-05concretizer: adjust integrity constraints to only apply to builds.Todd Gamblin1-6/+13
Many of the integrity constraints in the concretizer are there to restrict how solves are done, but they ignore that past solves may have had different initial conditions. For example, for things we're building, we want the allowed variants to be restricted to those currently in Spack packages, but if we are reusing a concrete spec, we need to be flexible about names that may have existed in old packages. Similarly, restrictions around compatibility of OS's, compiler versions, compiler OS support, etc. are really only about what is supported by the *current* set of compilers/build tools known to Spack, not about what we may get from concrete specs. - [x] restrict certain integrity constraints to only apply to packages that we need to build, and omit concrete specs from consideration.
2021-11-05concretizer: rework operating system semantics for installed packagesTodd Gamblin2-64/+104
The OS logic in the concretizer is still the way it was in the first version. Defaults are implemented in a fairly inflexible way using straight logic. Most of the other sections have been reworked to leave these kinds of decisions to optimization. This commit does that for OS's as well. As with targets, we optimize for target matches. We also try to optimize for OS matches between nodes. Additionally, this commit adds the notion of "OS compatibility" where we allow for builds to depend on binaries for certain other OS's. e.g, for macos, a bigsur build can depend on an already installed (concrete) catalina build. One cool thing about this is that we can declare additional compatible OS's later, e.g. CentOS and RHEL.
2021-11-05concretizer: `impose()` for concrete specs should use body facts.Todd Gamblin1-3/+3
The concretizer doesn't get a say in whether constraints from concrete specs are imposed, so use body facts for them.
2021-11-05include installed hashes in solve and optimize for reuseTodd Gamblin3-15/+104
2021-11-05rename `checked_spec_clauses()` to `spec_clauses()`Todd Gamblin1-8/+8
2021-11-05add `--reuse` option to `spack solve`Todd Gamblin2-6/+13
2021-11-04new package: librttopo (#27182)Sinan1-0/+24
Co-authored-by: sbulut <sbulut@3vgeomatics.com> Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
2021-11-04[New Package] Add Restic v0.12.1 (#27208)Alec Scott1-0/+28
Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
2021-11-04Rename the temporary scope for bootstrap buildcache (#27231)Massimiliano Culpo1-1/+1
If we don't rename Spack will fail with: ``` ImportError: cannot bootstrap the "clingo" Python module from spec "clingo-bootstrap@spack+python %gcc target=x86_64" due to the following failures: 'spack-install' raised ValueError: Invalid config scope: 'bootstrap'. Must be one of odict_keys(['_builtin', 'defaults', 'defaults/cray', 'bootstrap/cray', 'disable_modules', 'overrides-0']) Please run `spack -d spec zlib` for more verbose error messages ``` in case bootstrapping from binaries fails and we are falling back to bootstrapping from sources.
2021-11-04c3d: add new package (#27155)Ben Darwin1-0/+22
2021-11-04Add the spack tutorial environment as a cloud pipeline stack (#27137)Tamara Dahlgren2-0/+128
2021-11-04libfabric: add 1.13.2 (#27202)Jerome Soumagne1-0/+1
2021-11-04Sort arguments lexicographically in command's help (#27196)Massimiliano Culpo1-0/+5
2021-11-04exciting: add "oxygen" version, multiple fixes (#27217)downloadico1-18/+53
ensure that none of ^intel-mkl, ^intel-mpi, and ^mkl are used, unless the compiler is intel. Fix bad logic in the src/src_xs/m_makespectrum.f90 file in the oxygen version. Add the -fallow-argument-mismatch for gcc >= 10.
2021-11-04omega-h: add support for stand-alone testing (#26931)Cameron Smith1-4/+25
Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
2021-11-04Add new versions for HOHQMesh and switch to tar-ball releases (#27194)Joe Schoonover1-4/+5
Co-authored-by: Tamara Dahlgren <35777542+tldahlgren@users.noreply.github.com>
2021-11-04Add RelWithDebInfo to protobuf build_type list. (#27220)Jon Rood1-1/+1
2021-11-04Feature/exaworks spack (#27216)Andre Merzky1-1/+0
* add exaworks spack meta package * add maintainer * switch to `BundlePackage` * flake8 * another flake8 fix * remove incorrect dependency
2021-11-04mfem, hpx: fix recipes after conditional variants (#27215)Massimiliano Culpo2-4/+7
2021-11-04kokkos: refactor defines to use helper functions (#27189)Seth R. Johnson1-33/+19
2021-11-03ssht: New version 1.5.1 (#27173)Erik Schnetter1-1/+2
2021-11-03scr: 3.0rc2 release, variants and deps updates (#27178)Cameron Stanavige1-81/+140
* scr: 3.0rc2 release, variants and deps updates This adds 3.0rc2 release for end users to aid in testing scr for upcoming 3.0 release. Included in this change: - Require most recent component versions for this release - Add a variant for PDSH as it is now an optional dependency with this release - Add bbapi and datawarp (dw) variants - bbapi_fallback variant now requires bbapi variant with latest release - Add variants to enable/disable examples and tests - Add shared variant and current conflicts with ~shared - Update cmake_args to account for added variants where needed Additional updates: - Add maintainers - Use lists and for loops to clean up repetitive code involving all components - Use self.define and self.define_from_variant to clean up cmake_args - Use consistent quoting throughout package * Un-deprecate v2 and legacy * Use new conditional variants
2021-11-03simulationio package: add variants asdf, hdf5, rnpl, silo (#27172)Erik Schnetter1-3/+9
Define new variants asdf, hdf5, rnpl, silo to allow disabling or enabling dependencies.
2021-11-03hwloc: New version 2.6.0 (#27170)Erik Schnetter1-0/+1
2021-11-03mpitrampoline: New version 2.2.0 (#27171)Erik Schnetter1-0/+3
2021-11-03shtools: disable libtool, add 4.9.1, fix --test=root (#27014)Erik Schnetter2-0/+26
The Makefile expects the "other" libtool, not the GNU libtool we have in Spack. Closes https://github.com/spack/spack/issues/26993 Co-authored-by: Bernhard Kaindl <bernhardkaindl7@gmail.com>
2021-11-03tfel and mgis: add new versions and fix tests (#27011)Thomas Helfer2-2/+56
Co-authored-by: Bernhard Kaindl <bernhardkaindl7@gmail.com>
2021-11-03new package: telegraf (#27201)Andrew W Elble1-0/+22
2021-11-03Add Caliper v2.7.0 (#27197)David Boehme1-1/+2
2021-11-03trilinos: mark conflicts in @:13.1+tpetra^cuda@11 (#27188)Seth R. Johnson1-1/+4
* trilinos: fix @13.0.1+tpetra^cuda@11 * Mark CUDA conflict with old versions and always define TPL * trilinos: patch doesn't build so just mark as conflict
2021-11-03WarpX: 21.11 (#27158)Axel Huebl2-2/+4
Update `warpx` & `py-warpx` to the latest release, `21.11`.
2021-11-03nemsio package: add version 2.5.4; add option to build without MPI (#27030)Kyle Gerheiser1-2/+14
Version 2.5.4 adds an option which allows Nemsio to be built without MPI
2021-11-03r-reprex: add 2.0.1 (#27174)Manuela Kuhn1-12/+26
2021-11-03petsc, py-petsc4py: add versions 3.16.1 (#27152)Satish Balay2-0/+2
2021-11-03py-datalad: add 0.15.3 (#27193)Manuela Kuhn1-0/+1