| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
- We don't currently make enough use of the maintainers field on
packages, though we could use it to assign reviews.
- add a command that allows maintainers to be queried
- can ask who is maintaining a package or packages
- can ask what packages users are maintaining
- can list all maintained or unmaintained packages
- add tests for the command
|
|
|
|
I needed to add py-setuptools to get py-absl-py to build.
|
|
Freetype-2.8 and above use __builtin_shuffle which is not supported by
icc.
|
|
* perl: perl package takes in spack cflags.
* fix for flake8 test.
|
|
|
|
|
|
* Add QMCPACK v. 3.8.0
* Remove QE variant conflict for serial QMCPACK installations.
* Add support for QE 6.4.1 converter.
* FindLibxml2QMC patch function only needed prior to QMCPACK 3.8.0
|
|
While the c-blosc library compiles with icc some of the c-blosc tests do
not. Disable the tests so that the spack build can continue.
|
|
|
|
* Added a unit test reproducing the failure in 12085
* Fixed name clash in the 'from_environment_diff' function
The bug reported in #12085 stemmed from a name clash among variables,
introduced during the refactor in #10753 and not caught by unit tests
and reviews.
|
|
|
|
* relion - added v 3.0.7 and removed deprecated versions that have inferior performance
* relion 3.0.7 does require cuda 9 or above
|
|
|
|
|
|
|
|
* Add support for QE 6.4.1
* QE 6.3. backports branch no longer relevant.
* List QE develop first.
|
|
|
|
* Provide better error message when matching externals are found for package marked not buildable
|
|
* ioapi: add version 3.2
* ioapi: unwrap version checksum; it's exempt from line length QA
* ioapi: drop overridden build(); it's the same as the default
|
|
|
|
|
|
|
|
|
|
- Add `spack pkg changed` to show changed and added packages for a
commit.
- Make `spack pkg` support tests better.
|
|
https://github.com/openucx/ucx/releases/tag/v1.6.0
Released 2019-07-17
Verification builds on LANL Darwin x86_64 and Power9:
dantopa@cn2037:pr-update-ucx.spack $ date
Mon Jul 22 17:04:14 MDT 2019
dantopa@cn2037:pr-update-ucx.spack $ pwd
/scratch/users/dantopa/repos/spack/pr-update-ucx.spack
dantopa@cn2037:pr-update-ucx.spack $ spack find -ldf ucx
==> 2 installed packages
-- linux-centos7-x86_64 / gcc@4.8.5 -----------------------------
w7fp4n6 ucx@1.6.0%gcc
tt2hkol ^numactl@2.0.12%gcc
srhy7ry ^rdma-core@20%gcc
kvgvhpv ^libnl@3.3.0%gcc
-- linux-rhel7-ppc64le / gcc@4.8.5 ------------------------------
cji3ce7 ucx@1.6.0%gcc
pmgndwh ^numactl@2.0.12%gcc
qymrwx6 ^rdma-core@20%gcc
2263pm5 ^libnl@3.3.0%gcc
Signed-off-by: Daniel Topa <dantopa@lanl.gov>
|
|
|
|
* cmake: Move cxx11 flags for fujitsu into the flag_handler method
* cmake: sanitization and error checking in flag_handler
* cmake: Fix fujitsu flag check from 'fc' to 'fj'
|
|
|
|
* Fix version scraping for CRAN packages
* Remove set literals
|
|
- Setting specs from lockfiles was not correctly stringifying concretized
user specs.
- Fix `_set_user_specs_from_lockfile`
- Add some validation code to `SpecList` constructor
|
|
Spack has evolved to have three types of hash functions, and it's
becoming hard to tell when each one is called. Whlie we aren't yet ready
to get rid of them, we can refactor them so that the code is clearer and
easier to track.
- Add a `hash_types` module with concise descriptors for hashes.
- Consolidate hashing logic in a private `Spec._spec_hash()` function.
- `dag_hash()`, `build_hash()`, and `full_hash()` all call `_spec_hash()`
- `to_node_dict()`, `to_dict()`, `to_yaml()` and `to_json()` now take a
`hash` parameter consistent with the one that `_spec_hash()` requires.
Co-authored-by: Todd Gamblin <tgamblin@llnl.gov>
|
|
- ensure that Spec._build_hash attr is defined
- add logic to compute _build_hash when it is not already computed (e.g. for specs prior to this PR)
- add test to ensure that different instance of a build dep are preserved
- test conversion of old env lockfile format to new format
- tests: avoid view creation, DAG display in tests using MockPackage
- add regression test for more-general bug also fixed by this PR
- update lockfile version since the way we are maintaining hashes has changed
- write out backup for version-1 lockfiles and test that
|
|
* openjdk
* Removing preferred from latest and adding a few lines for readability.
* Remove bad whitesapce
* removing formatting changes
* stable url for openjdk 1.8
* remove extra blank line
* actual binary
|
|
|
|
|
|
Add version for 'gpu' and variant for 'cuda'. These are currently available from the 'master-gpu' branch.
* hpctoolkit: add version gpu and variant cuda
* The gcc >= 4.8.x requirement only applies for dyninst >= 10.x.
|
|
* libsharp: Don't add -march=native on ARM
* Add preferred=True to version 1.0.0.
|
|
* fix docker builds/remove extra builds/add ci builds
* preinstall vim in CI builder images
* simplify & streamline docker resources
* restore os-container-mapping.yaml file
|
|
|
|
The database and mutable_database fixtures were installing and uninstalling the same specs multiple times to ensure the database for tests has the correct state.
This commit optimizes the procedure by caching the state in an external directory, and copying it in instead of going through the installation or uninstallation again.
The database fixture is meant not to be modified by tests. This commit enforces this invariant by making the database read-only before starting the test.
* Added missing db markers to tests
* Added test for uninstall_by_spec
* `database` fixture now returns a read-only database
* Tests that modify the DB now use `mutable_database` fixture
|
|
ibm-java: fix the URL to only use a machine type that ibm-java
supports so that 'spack info' doesn't report a non-existent URL on
platforms that it doesn't support.
|
|
|
|
Summary:
- Allow multiple definitions of compiler in compilers.yaml (use first instance)
- Still print debug messages when there are duplicates, to assist users in finding this issue.
Merging configs from different scopes can result in multiple compiler being present in the same configuration list. Instead of raising when there are duplicates, take the one with highest precedence.
Print a debug message instead of raising, so that we can still diagnose this. We don't have a good way of warning the user about inconsistent configuration *in the same file* -- we'd need to dig into YAML file/line info for that.
|
|
- [x] Add shell tests to ensure that `spack env activate`, `spack env
deactivate`, and `despacktivate` continue to work.
- [x] Also ensure that activate and deactivate both work with `set -u`
|
|
(#12051)
Fixes #8908, 11844
Use Python MRO to find patch files from parent classes.
|
|
Fixes #12026
These are required on some systems
|
|
* extends mkdirs with permissions for intermediate folders
Does not use os.makedirs mode parameter because its behavior is changed
with Python 3.7 (it ignores it for intermediate dirs), and moreover it
was not possible to set different modes for newly-created folders
and leaf folder.
reference:
- https://bugs.python.org/issue19930
- https://docs.python.org/3.7/library/os.html#os.makedirs
* comment mkdirp step easing code understanding
* revert mkdir to default for package metapath
since metapath is nested in package folder, there is no need
to specify permissions for intermediate folders because the prefix
already exists.
* comment create_install_directory package modes
|
|
|
|
* If gettext is installed in the system it won't be in the spec tree.
|
