| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Fixes #9166
This is intended to reduce errors related to lock timeouts by making
the following changes:
* Improves error reporting when acquiring a lock fails (addressing
#9166) - there is no longer an attempt to release the lock if an
acquire fails
* By default locks taken on individual packages no longer have a
timeout. This allows multiple spack instances to install overlapping
dependency DAGs. For debugging purposes, a timeout can be added by
setting 'package_lock_timeout' in config.yaml
* Reduces the polling frequency when trying to acquire a lock, to
reduce impact in the case where NFS is overtaxed. A simple
adaptive strategy is implemented, which starts with a polling
interval of .1 seconds and quickly increases to .5 seconds
(originally it would poll up to 10^5 times per second).
A test is added to check the polling interval generation logic.
* The timeout for Spack's whole-database lock (e.g. for managing
information about installed packages) is increased from 60s to
120s
* Users can configure the whole-database lock timeout using the
'db_lock_timout' setting in config.yaml
Generally, Spack locks (those created using spack.llnl.util.lock.Lock)
now have no timeout by default
This does not address implementations of NFS that do not support file
locking, or detect cases where services that may be required
(nfslock/statd) aren't running.
Users may want to be able to more-aggressively release locks when
they know they are the only one using their Spack instance, and they
encounter lock errors after a crash (e.g. a remote terminal disconnect
mentioned in #8915).
|
|
|
|
* petsc: add new versions 3.9.4 and 3.10.0
* petsc:update superlu_dist dependency for version 3.10 [might have to change this later for xsdk]
* slepc: add in new releases 3.9.2 and 3.10.0
|
|
compilers (#9316)
|
|
|
|
|
|
- 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>
|
|
|
|
* adding r-animation package
|
|
|
|
|
|
|
|
|
|
|
|
* Catch2: 2.3.0+
Add the latest two releases of Catch2.
In 2.3.0+, the include changed to a future-proof
`<catch2/catch.hpp>` path which dependent projects will break upon.
* openPMD-api: Catch2 2.3.0+
openPMD-api just updated to use the new, future-proof Catch2
headers `<catch2/catch.hpp>`.
|
|
When a Spack Executable was configured to capture stderr and the
process failed, the error messages of the process were discarded.
This made it difficult to understand why the process failed. The
exception is now updated to include the stderr of the process when
the Executable captures stderr.
|
|
|
|
Adds 'code' to the list of suffixes that are excluded from version
parsing of URLs, such that if a URL contains the string
'cistem-1.0.0-beta-source-code', a version X will substitute in to
produce a URL with cistem-X-source-code ('source' was already excluded).
The 'cistem' package version is updated to make use of this (and fix
a fetching bug with the cistem package). A unit test is added to check
this parsing case.
|
|
Added variants for: mpi support, clang skeletonizer, building as
static and/or shared, and more.
|
|
|
|
|
|
|
|
Turns out that there was a configury problem in libhio
which caused issues building the package on non-cray
systems, aka when using mpicc and friends.
Signed-off-by: Howard Pritchard <hppritcha@gmail.com>
|
|
|
|
* candle-benchmarks: added v0.1
* ecp-proxy-apps: v1.0 now depends on candle-benchmarks@0.0
|
|
* star - added latest versions with shasum
* star - added latest versions with shasum
|
|
|
|
* Update rdma-core : new version and conflict with intel
* address review comments
|
|
|
|
This is required at least on RedHat/Fedora.
Many (most?) other people distribute gdb with this support enabled:
http://tomszilagyi.github.io/2018/03/Remote-gdb-with-stl-pp
https://bugzilla.redhat.com/show_bug.cgi?id=1596490
|
|
* add perl dependencies
* put bam2cfg in path
* fix perl dir
|
|
|
|
rdma-core requires pkg-config, otherwise libnl can not be found.
|
|
|
|
* Updating amrvis to allow building with profiling support.
* Setting MPI default to true.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
See: https://github.com/mariusmuja/flann/issues/369
|
|
* Charmpp: rename charm to charmpp according to ++ conventions
* modify packages that depend on charmpp
|
|
|
|
This commit adds a patch that prevents the package from hanging. The package would hang because CMakeLists would look for a system MPI. This patch changes the behavior.
|
|
|
|
|
|
|
|
|
|
|
