Age | Commit message (Collapse) | Author | Files | Lines |
|
Co-authored-by: sbulut <sbulut@3vgeomatics.com>
Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
|
|
|
|
PRs that change only package recipes will only run tests under "package_sanity.py" and without coverage. This should result in a huge drop the cpu-time spent in CI for most PRs.
|
|
|
|
|
|
* updated deps to get gtkplus to build
* gtk-doc requires docbook-xml 4.3
* patch gtk-doc build to find xml catalogs
* patch gtk-doc build to find xml catalogs
* patch gtk-doc build to find xml catalogs
* add new version, fix macOS build error
* reorder docbook versions from newest to oldest
Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
|
|
Signed-off-by: Tim Lane <tilne@amazon.com>
|
|
|
|
|
|
|
|
(#22350)
|
|
root 6.22 does not work with intel-tbb 2021.1.1.
So:
* Introduce conflicts()
(a fitting depends_on in the comments, but does not help with the classic conretizer.)
* Mark 2020.3 as preferred to help concretizer, when newer versions come up.
* Previous discussion:
https://github.com/spack/spack/pull/22263#issuecomment-797606475
* Relevant ROOT issue:
https://github.com/root-project/root/issues/6933
|
|
|
|
|
|
|
|
|
|
|
|
* py-yt: 3.6.1
The latest bugfix release of yt-project fixes issues with matplotlib
version 3.3.0+.
* py-yt: add many more version constrains
|
|
|
|
|
|
|
|
* Improved amber package. Added amber20
* Corrected description link between ambertools and amber versions
* Fixed ambertools handling
* Apply pathes only when problematic traget requested
* fixed style issue
* Added amber20 sha256 checksum
* Improved documentation
* Removed preferred amber18
* Changef f-string to str.format()
* Changef f-string to str.format()
* removed url_for_version fuction
|
|
|
|
|
|
|
|
|
|
|
|
|
|
A mitigation of a known issue that affects v3.0 is added, see
https://developer.amd.com/wp-content/resources/AOCC-3.0-Install-Guide.pdf
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
See #22330
|
|
|
|
|
|
|
|
fixes #19625 again
|
|
|
|
|
|
Before this fix, `spack containerize` complains that `centos/7` is invalid
(should have been `centos:7`)
|
|
* Added 2 new configure patch files to build WRF 3.9.1.1 and 4.2
with aocc@3.0
* Renamed patch files used for building WRF 3.9.1.1 and 4.2 with
aocc@2.3 (mostly, this also removes -march=native from AOCCOPT
and updates LIBMVEC options for aocc@2.3)
|
|
event (#22324)
|
|
* unit tests: mark slow tests as "maybeslow"
This commit also removes the "network" marker and
marks every "network" test as "maybeslow". Tests
marked as db are maintained, but they're not slow
anymore.
* GA: require style tests to pass before running unit-tests
* GA: make MacOS unit tests fail fast
* GA: move all unit tests into the same workflow, run style tests as a prerequisite
All the unit tests have been moved into the same workflow so that a single
run of the dorny/paths-filter action can be used to ask for coverage based
on the files that have been changed in a PR. The basic idea is that for PRs
that introduce only changes to packages coverage is not necessary, this
resulting in a faster execution of the tests.
Also, for package only PRs slow unit tests are skipped.
Finally, MacOS and linux unit tests are now conditional on style tests passing
meaning that e.g. we won't waste a MacOS worker if we know that the PR has
flake8 issues.
* Addressed review comments
* Skipping slow tests on MacOS for package only recipes
* QA: make tests on changes correct before merging
|
|
* py-aiobotocore: New package
* py-aiobotocore: Added python dependencies, and Removed unnecessary whitespace
|
|
In most cases, we want condition_holds(ID) to imply any imposed
constraints associated with the ID. However, the dependency relationship
in Spack is special because it's "extra" conditional -- a dependency
*condition* may hold, but we have decided that externals will not have
dependencies, so we need a way to avoid having imposed constraints appear
for nodes that don't exist.
This introduces a new rule that says that constraints are imposed
*unless* we define `do_not_impose(ID)`. This allows rules like
dependencies, which rely on more than just spec conditions, to cancel
imposed constraints.
We add one special case for this: dependencies of externals.
|
|
We only consider test dependencies some of the time. Some packages are
*only* test dependencies. Spack's algorithm was previously generating
dependency conditions that could hold, *even* if there was no potential
dependency type.
- [x] change asp.py so that this can't happen -- we now only generate
dependency types for possible dependencies.
|