summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2021-08-09Add a badge for the Boostrapping workflow (#25318)Massimiliano Culpo1-0/+1
This workflow is run daily on `develop`.
2021-08-09Make spack env activate x idempotent (#25222)Harmen Stoppels1-1/+2
* Make spack env activate x idempotent * Update lib/spack/spack/cmd/env.py
2021-08-09sos: shr-atomics is a disable/enable (#25315)Robert Cohn1-1/+1
2021-08-09giflib: define prefix and libversion also when building (#25263)iarspider1-6/+16
2021-08-09sos: add xpmem variant (#25260)Robert Cohn1-2/+10
Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com>
2021-08-09intel-oneapi-vtune: new package + remove danvev from maintainers (#25311)Vasily Danilin12-11/+40
2021-08-09xwidgets: add new package (#25237)Tom Stitt1-0/+24
2021-08-09libxc: add std flag for Intel (#25281)downloadico1-2/+4
2021-08-09dd4hep: fixes to run tests (#25204)Valentin Volkl1-0/+13
2021-08-09ispc: add v1.16 and v1.16.1 (#25206)Martin Aumüller1-3/+6
Aso adapt dependencies for older versions
2021-08-09cp2k: update elpa and sirius dependencies, fix build with mpich and gcc@10 ↵Tiziano Müller2-28/+52
(#24376) * cp2k: fix build with GCC-10+ and MPICH * cp2k: update SIRIUS and ELPA dependencies * elpa: add version 2021.05.001, add ROCm support, include SVE flags
2021-08-09xeus: add v1.0.4, improved package recipe (#24984)Tom Stitt1-9/+30
Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com> Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2021-08-09py-pydeprecate: add v0.3.1 (#25231)Adam J. Stewart1-0/+1
2021-08-09py-pytorch-lightning: add v1.4.1 (#25232)Adam J. Stewart1-6/+13
2021-08-09xproperty: add new package (#25236)Tom Stitt1-0/+25
2021-08-09py-pytest: add v6.2.4 (#25240)Adam J. Stewart1-22/+26
2021-08-09py-requests-unixsocket: add missing py-pbr dependency (#25241)Adam J. Stewart1-0/+1
2021-08-09ssht: add v1.5.0 (#25247)Erik Schnetter1-0/+1
2021-08-09py-setuptools: add v57.4.0 (#25239)Adam J. Stewart2-12/+15
2021-08-09dcm2niix: new package (at version 1.0.20210317) (#25250)Ben Darwin1-0/+16
2021-08-09apex: add v2.4.1 (#25248)Severin Strobl1-3/+4
Also updated the URLs for APEX according to the recent move.
2021-08-09casacore: add variant for ADIOS2 support (#25251)Martin Pokorny1-0/+7
2021-08-09installation: filter padding from all `tty` outputTodd Gamblin5-44/+111
This is both a bugfix and a generalization of #25168. In #25168, we attempted to filter padding *just* from the debug output of `spack.util.executable.Executable` objects. It turns out we got it wrong -- filtering the command line string instead of the arg list resulted in output like this: ``` ==> [2021-08-05-21:34:19.918576] ["'", '/', 'b', 'i', 'n', '/', 't', 'a', 'r', "'", ' ', "'", '-', 'o', 'x', 'f', "'", ' ', "'", '/', 't', 'm', 'p', '/', 'r', 'o', 'o', 't', '/', 's', 'p', 'a', 'c', 'k', '-', 's', 't', 'a', 'g', 'e', '/', 's', 'p', 'a', 'c', 'k', '-', 's', 't', 'a', 'g', 'e', '-', 'p', 'a', 't', 'c', 'h', 'e', 'l', 'f', '-', '0', '.', '1', '3', '-', 'w', 'p', 'h', 'p', 't', 'l', 'h', 'w', 'u', 's', 'e', 'i', 'a', '4', 'k', 'p', 'g', 'y', 'd', 'q', 'l', 'l', 'i', '2', '4', 'q', 'b', '5', '5', 'q', 'u', '4', '/', 'p', 'a', 't', 'c', 'h', 'e', 'l', 'f', '-', '0', '.', '1', '3', '.', 't', 'a', 'r', '.', 'b', 'z', '2', "'"] ``` Additionally, plenty of builds output padded paths in other plcaes -- e.g., not just command arguments, but in other `tty` messages via `llnl.util.filesystem` and other places. `Executable` isn't really the right place for this. This PR reverts the changes to `Executable` and moves the filtering into `llnl.util.tty`. There is now a context manager there that you can use to install a filter for all output. `spack.installer.build_process()` now uses this context manager to make `tty` do path filtering when padding is enabled. - [x] revert filtering in `Executable` - [x] add ability for `tty` to filter output - [x] install output filter in `build_process()` - [x] tests
2021-08-09py-speech-recognition: new package (#25273)Jen Herting1-0/+19
2021-08-09netcdf-fortran: fix building with AOCC (#25186)Sergey Kosukhin1-0/+39
2021-08-09mfem: add v4.3 (#25158)Tom Stitt1-2/+5
Co-authored-by: Veselin Dobrev <dobrev@llnl.gov>
2021-08-09ci pipelines: expand the list of RADIUSS packages (#25282)Tamara Dahlgren1-10/+10
2021-08-09trilinos: fix +hypre build (#25291)Satish Balay1-1/+1
2021-08-09petsc: fix build with trilinos (#25289)Satish Balay1-1/+1
2021-08-09Update rocm ecosystem to v4.3.0 (#25299)Sreenivasa Murthy Kolam12-21/+33
2021-08-09petsc, petsc4py: add version 3.15.3 (#25307)Satish Balay2-0/+2
2021-08-09r-cairo: add an explicit dependency on libxt (#25309)Glenn Johnson1-0/+2
Since r-cairo will always look for X libraries, and likely find them on the system, make it always depend on r+X.
2021-08-09hip: fix broken tests with ^cmake@3.21: (#25246)Harmen Stoppels5-0/+236
2021-08-09Use __skip_rocmclang for cmake 3.21 in rocblas/rocfft to avoid incomplete ↵Harmen Stoppels2-0/+8
compiler support (#25253)
2021-08-09libtree: add v1.2.3 (#25270)Harmen Stoppels1-0/+1
2021-08-08Remove xsdk@0.2.0 and associated versions and xsdktrilinosSeth R Johnson8-103/+0
These versions can cause weird concretizations, and it looks like the old version of xsdk may not even work because of xsdktrilinos being disabled. The hypre version tagged for xsdk@0.2 no longer exists at the described location.
2021-08-08trilinos: remove develop version, change xsdk nameSeth R Johnson3-15/+14
With the previous naming scheme, `trilinos@:10` concretizes to `trilinos@xsdk-0.2.0`. Now, it's clear what the xsdk version is closest to. Changed from tag to the corresponding commit SHA for safety.
2021-08-08petsc: cleanup test code to support 'spack test run' and add a 'cuda' test ↵Satish Balay1-48/+49
(#25099)
2021-08-08Clean Up PR from Container BuilderAlec Scott1-9/+2
2021-08-08hwloc: Adding opencl and rocm (AMD GPUs) variants to hwloc.Edgar A. Leon1-6/+21
2021-08-08trilinos: flag_handler logic fix (#25290)lukebroskop1-1/+2
* Do not allow cray build system patch for later version of otf2 * Modify flag_handler logic in the trilinos package Modify flag_handler logic in the trilinos package to work better with compilers other than CCE
2021-08-08vecgeom: new version 1.1.16 (#25266)Wouter Deconinck1-0/+1
Diff 1.1.15 to 1.1.16 at https://gitlab.cern.ch/VecGeom/VecGeom/-/compare/v1.1.15...v1.1.16?from_project_id=981, no changes to build dependencies.
2021-08-07Fix GHCR Username in Container Builder (#25301)Alec Scott1-1/+1
2021-08-06openPMD-api: CTest & Install Tests (#25300)Axel Huebl1-0/+20
Run CTest at build time with: ``` spack install --test=root openpmd-api@<version> ``` and run smoke-tests after install and loading of the package via ``` spack load -r /<spec> spack test run /<spec> ```
2021-08-06openPMD-api: 0.14.1 (#25265)Axel Huebl1-0/+1
* openPMD-api: 0.14.1 Add the latest bugfix release. * Keep 0.13.4 still preferred More regressions to mitigate...
2021-08-06WarpX: 21.08 (#25234)Axel Huebl2-1/+3
Add the latest WarpX release.
2021-08-06Add New Build Containers Workflow (#24257)Alec Scott2-1/+80
This pull request adds a new workflow to build and deploy Spack Docker containers from GitHub Actions. In comparison with our current system where we use Dockerhub's CI to build our Docker containers, this workflow will allow us to now build for multiple architectures and deploy to multiple registries. (At the moment x86_64 and Arm64 because ppc64le is throwing an error within archspec.) As currently set up, the PR will build all of the current containers (minus Centos6 because those yum repositories are no longer available?) as both x86_64 and Arm64 variants. The workflow is currently setup to build and deploy containers nightly from develop as well as on tagged releases. The workflow will also build, but NOT deploy containers on a pull request for the purposes of testing this PR. At the moment it is setup to deploy the built containers to GitHub's Container Registry although, support for also uploading to Dockerhub/Quay can be included easily if we decide to keep releasing on Dockerhub/want to begin releasing on Quay.
2021-08-06[py-sentencepiece] added veriosn 0.1.91 (#25275)Jen Herting1-0/+2
2021-08-06codecov: allow coverage offsets for more base commit flexibility (#25293)Todd Gamblin1-0/+13
This is an attempt to fix "Missing base commit" messages in the codecov UI. Because we do not run full tests on package PRs, package PRs' merge commits on `develop` don't have coverage info. It appears that codecov will give you an error if the pseudo-base's coverage data doesn't all apply properly to the real PR base, unless the `allow_coverage_offsets` option is set. * See here for docs: https://docs.codecov.com/docs/comparing-commits#pseudo-comparison * See here for another potential solution: https://community.codecov.com/t/2480/15
2021-08-06refactor: rename `colorful` kwarg to `color` (#25292)Todd Gamblin1-30/+18
`compare_specs()` had a `colorful` keyword argument, but everything else in spack uses `color` for this. - [x] rename the argument - [x] make the default follow spack's `--color=always/never/auto` setting