summaryrefslogtreecommitdiff
path: root/share
AgeCommit message (Collapse)AuthorFilesLines
2019-01-10spack versions: only list safe versions (#10004)Adam J. Stewart1-1/+1
* spack versions: only list safe versions * Add unit tests for spack versions -s
2019-01-01copyright: update license headers for 2013-2019 copyright.Todd Gamblin23-23/+23
2018-12-30commands: add `spack resource` command to inspect downloadable filesTodd Gamblin1-0/+26
- currently just looks at patches - allows you to find out which package applied a patch to a spec - intended to work with tarballs and resources in the future. - add tab completion for `spack resource` and subcommands
2018-12-29coverage: use kcov to get coverage for our cc scriptTodd Gamblin2-1/+26
2018-12-20Fix docker builds (#9805)Omar Padron2-7/+67
* move docker test logic to share/spack/qa * update Dockerfile for archlinux
2018-12-20fix multiple issues with the docker images (#9718)Omar Padron4-2/+24
- fixed an issue where some undesirable parts of the spack source tree were being copied into the image context. - added a workaround for a tty ioctl warning on ubuntu - adjusted how the main images are built so that `RUN spack ...` works automatically for child images that base themselves on them.
2018-12-20Report current git commit of Spack to CDashZack Galbreath1-4/+7
When using the CDash reporter, upload a Update.xml file that indicates the hash of Spack's current git commit.
2018-12-20Allow more customization for CDash reporterZack Galbreath2-4/+4
Add new command line arguments to `spack install` that allow users to set the build name, site name, and track in their CDash report.
2018-12-17Update Spack's Bash completion script (#10114)Adam J. Stewart1-35/+171
* Update Spack's Bash completion script * spack mirror create options changed
2018-12-15env setup: support --help for cd/env commands (#10069)Matthias Diener1-2/+2
2018-12-15.travis.yml: enable ccache (#6370)Christoph Junghans1-0/+2
2018-12-14Turn on verbose output for MPICH builds in Travis (#10105)Massimiliano Culpo1-1/+5
Lately many CI runs for PRs are failing due to the `mpich` build that times out on Travis (10 mins. without output). As the timeout seems to happen consistently during the build phase, increasing the verbosity of that test can help working around the issue.
2018-12-04fix: adapt junit template to escape std{out,err} (#9935)Matthias Wolf1-4/+4
2018-11-09env: environments can be named or created in directoriesTodd Gamblin2-4/+5
- `spack env create <name>` works as before - `spack env create <path>` now works as well -- environments can be created in their own directories outside of Spack. - `spack install` will look for a `spack.yaml` file in the current directory, and will install the entire project from the environment - The Environment class has been refactored so that it does not depend on the internal Spack environment root; it just takes a path and operates on an environment in that path (so internal and external envs are handled the same) - The named environment interface has been hoisted to the spack.environment module level. - env.yaml is now spack.yaml in all places. It was easier to go with one name for these files than to try to handle logic for both env.yaml and spack.yaml.
2018-11-09env: add spack env activate/deactivate and shell supportTodd Gamblin3-1/+80
- `spack env activate foo`: sets SPACK_ENV to the current active env name - `spack env deactivate`: unsets SPACK_ENV, deactivates the environment - added support to setup_env.sh and setup_env.csh - other env commands work properly with SPACK_ENV, as with an environment arguments. - command-line --env arguments take precedence over the active environment, if given.
2018-10-29setup-env: Avoid different output format of `ps` (#9629)Bert Wesarg1-1/+1
setup-env includes a call to 'ps' to determine what shell is being used. 'ps' can be instructed to use a different default output format via the 'PS_FORMAT' env variable. Thus unset this variable before calling 'ps'.
2018-10-26docker: unite Dockerfiles; auto-deploy images to DockerHub (#9329)Omar Padron24-408/+442
* Unite Dockerfiles - add build/run/push scripts * update docker documentation * update .travis.yml * switch to using a preprocessor on Dockerfiles * skip building docker images on pull requests * update files with copyright info * tweak when travis builds for docker files are done
2018-10-17relicense: add `spack license` commandTodd Gamblin1-0/+4
- `spack license list-files`: list all files that should have license headers - `spack license list-lgpl`: list files still under LGPL-2.1 - `spack license verify`: check that license headers are correct - Added `spack license verify` to style tests
2018-10-17relicense: replace LGPL headers with Apache-2.0/MIT SPDX headersTodd Gamblin13-69/+67
- remove the old LGPL license headers from all files in Spack - add SPDX headers to all files - core and most packages are (Apache-2.0 OR MIT) - a very small number of remaining packages are LGPL-2.1-only
2018-09-24travis: require sudo in an attempt to avoid build timeouts (#9327)Todd Gamblin1-1/+5
- Many container builds are timing out frequently during Spack tests in Travis CI. - Travis recommends to try `sudo: required` to see whether this is an infrastructure issue or something else. - added `sudo: required` to all Linux builds. - added --verbose to `spack test` invocation so that we can see more easily what tests it's timing out on. Signed-off-by: Todd Gamblin <tgamblin@llnl.gov>
2018-08-14Csh: fix load/use commands (#8971)Matthias Diener1-4/+4
2018-08-07Fixing the addition curly brackets to conform to the rest of the templates ↵Micheal Quinn1-1/+1
usage of a literal curly bracket
2018-08-07Adding logic to the autoload if statement so it only fire if the module is ↵Micheal Quinn1-1/+1
being loaded.
2018-08-04Generate coverage reports for all unit and build testsAdam J. Stewart1-1/+1
2018-08-03Update bash completion with new spack arch flagsAdam J. Stewart1-1/+2
2018-08-01lmod: fix use of custom separator in prepend_path etc. (#8737)Stephen Herbein1-3/+3
fixes #8736
2018-07-27Fix shift warning on zsh (#8805)Michael Kuhn1-2/+10
When using zsh, trying to shift when there are no arguments left results in warnings like this: spack:shift:22: shift count must be <= $#
2018-07-24The auto-completion file is now consistent with `spack module`Massimiliano Culpo1-10/+124
2018-07-24Grouped all the module commands under `spack module`Massimiliano Culpo1-4/+4
As requested in the review all the commands meant to manage module files have been grouped under the `spack module` command. Unit tests have been refactored to match the new command structure.
2018-07-24module file tutorial: rebuilt docker image and updated the scriptMassimiliano Culpo1-2/+1
2018-07-24spack load exits with 1 if module does not exist or is not installedMassimiliano Culpo1-0/+8
fixes #2215 fixes #2570 fixes #6676 fixes #7281 closes #3827 This PR reverts the use of `spack module loads` in favor of `spack module find` when loading module files via Spack. After this PR `spack load` will accept a single spec at a time, and will be able to interpret correctly the `--dependencies` option.
2018-07-24Revert "Fix recursive module loading."Massimiliano Culpo1-4/+4
This reverts commit 732c24f603864ec7dbec425ac4507b47fdb7a641.
2018-07-22Remove extra Scientific Linux docker build left after merge. (#8770)Patrick Gartung4-247/+0
2018-07-18shell: Add spack to PATH before calling spack in setup-env.csh (#8740)Adam J. Stewart1-1/+1
2018-07-16add `spack --print-shell-vars` to speed up `setup-env.[c]sh` (#8101)Todd Gamblin2-21/+12
- The setup-env.sh script currently makes two calls to spack, but it should only need to make one. - Add a fast-path shell setup routine in `main.py` to allow the shell setup to happen in a single, fast call that doesn't load more than it needs to. - This simplifies setup code, as it has to eval what Spack prints - TODO: consider eventually making the whole setup script the output of a spack command
2018-06-26Docker dedupe (#8441)Omar Padron22-768/+125
* Add Dockerfile for Scientific Linux 7 (RHEL7 recompile) * revert version change * remove duplicate docker-related files
2018-06-26Add Dockerfile for Scientific Linux 7 (RHEL7 recompile) (#8422)Patrick Gartung5-0/+253
* Add Dockerfile for Scientific Linux 7 (RHEL7 recompile)
2018-06-24refactor: move templates from root to share/spackTodd Gamblin8-0/+308
- This complies with the unix directory hierarchy standard (which Spack attempts to follow) - Also unclutters the repo root directory.
2018-05-17config: simplify configuration API to just get and setTodd Gamblin2-4/+4
- replace `spack.config.get_configuration()` with `spack.config.config()` - replace `get_config`/`update_config` with `get`, `set` - add a path syntax that can be used to refer to specific config options without firt getting the entire configuration dict - update usages of `get_config` and `update_config` to use `get` and `set`
2018-04-24environment shell: fix `spack load` (#7747)René Widera1-6/+6
Fix `spack load` with extended packe specifications those includes spaces. Solved by using perfectly parameter forwarding via temporary array. example: ``` $ spack install zlib $ spack install zlib cppflags='-O3 -march=native' $ spack install zlib cppflags='-O2 -march=native' $ spack find -d -L -f zlib ==> 3 installed packages. -- linux-linuxmint18-x86_64 / gcc@5.4.0 ------------------------- k5hg4kkxiutkfl6n53ogz5wnlbdrsdtf zlib@1.2.11%gcc mse2fyzdxciszdhiqi4b5kl6fxkps3fh zlib@1.2.11%gcc cppflags="-O2 -march=native" vrnvj2fikcbxqxrymctnlpmud7wbuahk zlib@1.2.11%gcc cppflags="-O3 -march=native" $ spack load zlib cppflags='-O3 -march=native' ==> Error: Unexpected token ['zlib', 'cppflags=-O3', '-march=native'] ```
2018-04-17Autocomplete spack providers (#7783)Adam J. Stewart1-2/+5
2018-04-12Fixes conflicts in OSX nightly tests (#7732)Massimiliano Culpo1-1/+1
fixes #7593 Unit tests on OSX are trying to concretize mpileaks, and they fail due to a conflict in the package: "%gcc@7.2.0:" conflicts with "elfutils@0.163" This solves the issue asking explicitly to concretize against elfutils@1.170
2018-03-29update tests: concretize mpileaks with gcc (#7635)scheibelp1-1/+1
Fixes #7593 By default MacOS concretizes using the clang compiler. The unit tests include a call to "spack spec mpileaks", which has elfutils as a dependency; #7096 added a conflict in elfutils to avoid building with clang, which lead to the MacOS unit tests to start failing. This updates the concretization to force using gcc when concretizing mpileaks.
2018-03-25Various updates to Spack's Bash completion (#7590)Adam J. Stewart1-52/+175
* Various updates to Spack's Bash completion * Equals sign messes up tab completion
2018-03-24Update copyright on LLNL files for 2018. (#7592)Todd Gamblin3-3/+3
2018-03-06Save sources in a mirror and cache it in Travis (#7392)Massimiliano Culpo1-0/+6
2018-02-27Docker-Based Developer Resource (#5871)Omar Padron22-0/+1246
* add docker-based development resources * incorporate feedback from @ax3l * fix docs/improve ssh handling * experiment with custom prompt * add arch/fix missing core_compilers key * add centos/minor tweaks * make prompt experiment optional * workaround problem with latest fedora docker image * add docker documentation page to index toc * try another documentation fix * switch arch linux base to base/archlinux * update the git urls in the Dockerfiles * add opensuse * switch CUSTOM_PROMPT variable to simply "PROMPT"
2018-01-20Restore multiprocessing in unit tests (#6949)Massimiliano Culpo3-9/+1
* Revert "Travis: use --concurrency=multiprocessing only on build tests (#6872)" This reverts commit 596d463714d46929f81db62b171c5a772679bb12. * Removing 'coverage combine' in test script According to what was discovered in #6887, one of the problems is calling 'coverage combine' twice without the '-a' flag. This removes the first call within our test scripts.
2018-01-11Reduce verbosity of build tests (#6901)Adam J. Stewart1-1/+1
2018-01-10Travis: use --concurrency=multiprocessing only on build tests (#6872)Massimiliano Culpo1-1/+5
On a local workstation, it seems that tracking multiple processes during coverage may result in malformed coverage reports for unit tests and not for build tests. Given that multiple processes make a difference in coverage mainly for build tests, try to disable the tracking for unit tests to see if we get more stable coverage results.