| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* Don't spawn processes during python 2.6/2.7 'test_compiler_add' unit tests
* Travis seems to choke on the excessive parallelism in `compiler find`
|
|
|
|
- When returning string output, use text_type and decode utf-8 in Python
2 instead of using `str`
- This properly handles unicode, whereas before we would pass bad strings
to colify in `spack blame` when reading git output
- add a test that round-trips some unicode through an Executable object
|
|
* Remove /nfs/tmp2 from default configuration
* /nfs/tmp2 is going away from LC... and doesn’t exist for the rest of the world.
* update documentation to remove /nfs/tmp2 as well
|
|
* Record build output as an array of lines rather than concatenating to a
single large string.
* Use string.find to avoid running re.search on every line of output.
|
|
|
|
When using the CDash reporter, upload a Update.xml file that
indicates the hash of Spack's current git commit.
|
|
|
|
Pass extra data when submitting to CDash. If CDash responds with a buildId,
construct and display helpful URL that links to the uploaded report.
|
|
Add new command line arguments to `spack install` that allow users
to set the build name, site name, and track in their CDash report.
|
|
Make sure cdash_phase is defined before referring to it.
|
|
- some commands were missed in the rollout of spack environments
- this makes all commands that need to disambiguate specs restrict the
disambiguation to installed packages in the active environment, as
users would expect
|
|
Currently, only the Git repsository's URL shows up in the `spack info`
output, which makes it hard to distinguish different versions:
```
Safe versions:
develop [git] https://github.com/LLNL/H5Z-ZFP.git
0.8.0 [git] https://github.com/LLNL/H5Z-ZFP.git
0.7.0 [git] https://github.com/LLNL/H5Z-ZFP.git
```
This change adds additional information as shown when cloning a Git
repository:
```
Safe versions:
develop [git] https://github.com/LLNL/H5Z-ZFP.git on branch master
0.8.0 [git] https://github.com/LLNL/H5Z-ZFP.git at commit af165c4
0.7.0 [git] https://github.com/LLNL/H5Z-ZFP.git at commit 58ac811
```
|
|
* Add additional info to MesonPackage docs
* No Pygments lexer for Meson code, default to none
|
|
|
|
|
|
* This fixes a number of bugs:
* Patches were not properly downloaded and added to mirrors.
* Mirror create didn't respect `list_url` in packages
* Update the `spack mirror` command to add all packages in the
concretized DAG (where originally it only added the package specified
by the user). This is required in order to collect patches that are specified
by dependents. Example:
* if X->Y and X requires a patch on Y called Pxy, then Pxy will only
be discovered if you create a mirror with X.
* replace confusing --one-version-per-spec option for `spack mirror create`
with --versions-per-spec; support retrieving multiple versions for
concrete specs
* Implementation details:
* `spack mirror create` now uses regular staging logic to download files
into a mirror, instead of reimplementing it in `add_single_spec`.
* use a separate resource caching object to keep track of new
resources and already-existing resources; also accepts storing
resources retrieved from a cache (unlike the local cache)
* mirror cache object now stores resources that are considered
non-cachable, like (e.g. the tip of a branch);
* the 'create' function of the mirror module no longer traverses
dependencies since this was already handled by the 'mirror' command;
* Change handling of `--no-checksum`:
* now that 'mirror create' uses stages, the mirror tests disable
checksums when creating the mirror
* remove `no_checksum` argument from library functions - this is now
handled at the Spack-command-level (like for 'spack install')
|
|
|
|
* we weren't properly setting module variables for the root package in a DAG -- just for transitive dependencies.
|
|
|
|
|
|
Add tests MRO for inherited multimethods with multiple inheritance
Add tests for inherited and overridden multimethods
|
|
- all multimethod tests are now run for both `multimethod` and
`multimethod-inheritor`
- do this with a parameterized fixture (pkg_name) that runs the same
tests on both
|
|
- simplify logic in multimethod
- remove the requirement of multimethod invocations to walk up the stack.
|
|
- Since early Spack versions, the SpecParser has (weirdly) been
responsible for initializing Spec fields.
- This refactors initialization to take place in Spec.__init__, as it
probably should have originally.
- This makes the code easier to read, the parser easier to understand,
and removes the use of __new__ in the parser to initialize the Spec.
- This also makes it possible to make a completely empty Spec with
`Spec()` -- this is an abstract Spec that will match anything.
|
|
|
|
|
|
Fixes #9908
Spack was assembling flags in a manner that could in different
orderings for repeated concretizations of the same spec and config
|
|
|
|
* intel-mkl: fix usage of openmp_libs and tbb_libs
* intel-mkl: remove trailing whitespace from openmp lib
|
|
Found a couple bugs while trying to copy and paste the exact
tutorial content.
|
|
|
|
|
|
|
|
- tutorial goes through three sections:
- installing and uninstalling environments
- dealing with many specs
- spack.yaml and spack.lock and workflows
|
|
* Updates to Configuration Tutorial for SC18
* Suggested rewording
|
|
|
|
|
|
Grammar/spelling issues
|
|
* "spack install" now uses cache by default, update examples accordingly
* Replace some example packages with others
* Packing tutorial reference to "spack env" replaced with "spack build-env"
* Command line prompts in examples are shortened
* Example output (including paths) are updated to be more relevant to training environment
|
|
Update all examples that need an MPI provider to build with MPICH; reorganize so that fixing MPICH (as part of environment section) comes first in the tutorial (most examples in the tutorial use an MPI provider).
|
|
- previously, uninstall would complain if a spec was needed by an
environment.
- Now, we analyze dependents and dependent environments and simply remove
(not uninstall) specs that are needed by environments
|
|
- `spack install` was setting the root to be the concrete spec
- abstract spec is now preserved
|
|
- fix highlighting of roots in concretized specs in `spack find`
- tighten up the `spack find` output in environments
|
|
- with no arguments, these commands will now edit or dump the
environment's `spack.yaml` file.
- users may not know where named environments live
- this makes it convenient for users to get to the spack.yaml
configuration file for their named environment.
|
|
|
|
* Update Makefile to use property methods ("build_targets"/"install_targets")
to demonstrate their usage
* Fix highlighting
* Change cbench example to ESMF:
CBench package file was changed and no longer uses the example shown in
the old docs
|
|
Scopes added with -C are now referred to as "custom scopes"
rather than "command line scopes". "command line scope" now refers
to specific config options that are set on the command line (like
"--insecure")
|
|
- default is still to use the cache, but we've added back the
`--use-cache` argument so that scripts that used it are still correct.
- `--no-cache` is stil present and is mutually exclusive with `--use-cache`
|
|
* Introduce FFTW2 and FFT3 providers for Intel-MKL and FFTW Spack packages.
* make fftw default package for fftw-api virtual package
* virtual package test assertion now provides location of default virtual packages.
* Change name of virtual package to fftw-api and used versioned interface.
|
