Develop #122
Closed
Develop #122
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…pack#43089) * proj: correct CMake arg for shared build with proj older than 7.0.0 * Actually use new CMake arg * Update var/spack/repos/builtin/packages/proj/package.py Co-authored-by: Adam J. Stewart <[email protected]> --------- Co-authored-by: Adam J. Stewart <[email protected]>
…43103) Bumps [mypy](https://github.com/python/mypy) from 1.8.0 to 1.9.0. - [Changelog](https://github.com/python/mypy/blob/master/CHANGELOG.md) - [Commits](python/mypy@v1.8.0...1.9.0) --- updated-dependencies: - dependency-name: mypy dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…#43107) Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 5.1.0 to 5.2.0. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@4a13e50...af5a7ed) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* Remove dead code in spack * Remove dead code in llnl
* package/qgis: add new version * improve Qsci.pro * improve * fix undefined symbol qsciprinter error * add import test * fix bug * add version 3.36 * [@spackbot] updating style on behalf of Sinan81 * fix long line * only run import test when +python * first attempt at stand-alone test * add TODO --------- Co-authored-by: sbulut <[email protected]> Co-authored-by: Sinan81 <[email protected]> Co-authored-by: Sinan81 <Sinan@world>
* ruby: add version 3.3.0 * added dependency on libyaml
* geant4: new variant timemory * geant4: depends_on [email protected]: * geant4: fix style
* e4s ci stacks: add cp2k cpu and gpu specs * remove non-building cp2k specs
* py-earth2mip: add new package * Fix audit tests * Make things easier to concretize * Make things easier to concretize * Fix magics build * Fix onnx build * blacken * cmake > py-cmake * Fix onnxruntime build * onnxruntime: remove unknown cmake vars * Trick bazelisk into using Spack bazel * Different deps for main * protobuf: add v3.25.3 * Enforce upper bound on jaxlib version * py-chex: add v0.1.85 * py-dm-haiku: add v0.0.12 * py-jax: add v0.4.25 * Older jaxlib doesn't build on ppc64le either
* aocl-utils: source sha has changed * aocl-utils: version 4.1 hash updated
fixes spack#43097 Before this PR the behavior of mixins used together with builders was to mask completely the callbacks defined from the class coming later in the MRO. Here we fix the behavior by accumulating all callbacks, and de-duplicating them later.
* perl-parsetemplate: add new package * perl-parsetemplate: update to latest copyright date and add license
…ack#42157) * perl-math-symbolic: add required perl-parse-recdescent dependency * perl-math-symbolic: add new runtime dependency
Co-authored-by: Tamara Dahlgren <[email protected]>
* py-psyclone and py-fparser new releases added * py-fparser: add missing releases for py-psyclone * py-psyclone: actioned @adamjstewart comments * py-psyclone: removed py-pytest-pylint * py-pytest-pylint: added package @ latest version * py-pytest-pylint: reformatted * Update var/spack/repos/builtin/packages/py-psyclone/package.py Co-authored-by: Adam J. Stewart <[email protected]> * py-pytest-pylint: added build deps and runtime dep versions * py-pytest-pylint: removed version from setuptools * py-psyclone: add py-pytest-pylint test dep and alphabetize deps * Update var/spack/repos/builtin/packages/py-pytest-pylint/package.py Co-authored-by: Adam J. Stewart <[email protected]> * py-psyclone: deps ordered --------- Co-authored-by: Adam J. Stewart <[email protected]>
Needed to parse job options in yaml format (https://gitlab.cern.ch/gaudi/Gaudi/-/blob/master/GaudiKernel/python/GaudiKernel/ProcessJobOptions.py#L528). In principle this is optional, but it's needed for the test 35 - GaudiKernel.pytest.nose.test_Configurables (Failed). Seems like there's no harm done in adding this as a full dependency.
* added intel-oneapi-compilers * added classics version
Signed-off-by: Samuel K. Gutierrez <[email protected]>
* py-python-lsp-server: add v1.10.0 * Apply suggestions from code review Co-authored-by: Adam J. Stewart <[email protected]> * Remove py-wheel from package * Apply suggestions from code review Co-authored-by: Adam J. Stewart <[email protected]> --------- Co-authored-by: Adam J. Stewart <[email protected]>
* Changes to re-enable aws-pcluster pipelines - Use compilers from pre-installed spack store such that compiler path relocation works when downloading from buildcache. - Install gcc from hash so there is no risk of building gcc from source in pipleine. - `packages.yam` files are now part of the pipelines. - No more eternal `postinstall.sh`. The necessary steps are in `setup=pcluster.sh` and will be version controlled within this repo. - Re-enable pipelines. * Add and * Debugging output & mv skylake -> skylake_avx512 * Explicilty check for packages * Handle case with no intel compiler * compatibility when using setup-pcluster.sh on a pre-installed cluster. * Disable palace as parser cannot read require clause at the moment * ifort cannot build superlu in buildcache `ifort` is unable to handle such long file names as used when cmake compiles test programs inside build cache. * Fix spack commit for intel compiler installation * Need to fetch other commits before using them * fix style * Add TODO * Update packages.yaml to not use 'compiler:', 'target:' or 'provider:' Synchronize with changes in https://github.com/spack/spack-configs/blob/main/AWS/parallelcluster/ * Use Intel compiler from later version (orig commit no longer found) * Use envsubst to deal with quoted newlines This is cleaner than the `eval` command used. * Need to fetch tags for checkout on version number * Intel compiler needs to be from version that has compatible DB * Install intel compiler with commit that has DB ver 7 * Decouple the intel compiler installation from current commit - Use a completely different spack installation such that this current pipeline commit remains untouched. - Make the script suceed even if the compiler installation fails (e.g. because the Database version has been updated) - Make the install targets fall back to gcc in case the compiler did not install correctly. * Use generic target for x86_64_vX There is no way to provision a skylake/icelake/zen runner. They are all in the same pools under x86_64_v3 and x86_64_v4. * Find the intel compiler in the current spack installation * Remove SPACK_TARGET_ARCH * Fix virtual package index & use package.yaml for intel compiler * Use only one stack & pipeline per generic architecture * Fix yaml format * Cleanup typos * Include fix for ifx.cfg to get the right gcc toolchain when linking * [removeme] Adding timeout to debug hang in make (palace) * Revert "[removeme] Adding timeout to debug hang in make (palace)" This reverts commit fee8a01. * palace x86_64_v4 gets stuck when compiling try newer oneapi * Update comment * Use the latest container image * Update gcc_hashes to match new container * Use only one tag providing tags per extends call Also removed an unnecessary tag. * Move generic setup script out of individual stack * Cleanup from last commit * Enable checking signature for packages available on the container * Remove commented packages / Add comment for palace * Enable openmpi@5 which needs pmix>3 * don't look for intel compiler on aarch64
x264 does not publish releases so tag a newer commit in Spack in order to be able to use an up-to-date version.
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Cecilia Lau <[email protected]> Co-authored-by: Jen Herting <[email protected]>
…spack#42746) Enable OpenBLAS's built-in CPU capability detection and kernel selection. This allows run-time selection of the "best" kernels for the running CPU, rather than what is specified at build time. For example, it allows OpenBLAS to use AVX512 kernels when running on ZEN4, and built targeting the "ZEN" architecture. Co-authored-by: Branden Moore <[email protected]>
taken from the debian ncurses source package.
As the cmake build is triggered by scikit build, the usual spack option for enabling tests had no effect and the heavy test suite ran all the time. Used scikit-build/cmake-python-distributions#172 (comment) to implement how to pass options to the actual `cmake` build. I also excluded some tests that failed for me on alma9 (gcc 11.4.1), so the rest of the test suite can be run.
* elpa streams * [@spackbot] updating style on behalf of RMeli * Apply suggestions from @albestro * Update var/spack/repos/builtin/packages/elpa/package.py Co-authored-by: Mikael Simberg <[email protected]> --------- Co-authored-by: RMeli <[email protected]> Co-authored-by: Mikael Simberg <[email protected]>
* Make sure APEX_WITH_KOKKOS CMake option is set in apex * Add conflict for apex with ~kokkos
Signed-off-by: Bernhard Kaindl <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.