Bump actions/setup-python from 3.1.2 to 4.6.0 #69
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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Co-authored-by: mahendrapaipuri <[email protected]>
* kokkos-kernels: add variant 'shared' * Update var/spack/repos/builtin/packages/kokkos-kernels/package.py
* ci: Enable more packages in the DVSDK CI pipeline * doxygen: Add conflicts for gcc bugs * dray: Add version constraints for api breakage with newer deps
glib has a few tests which have external dependencies or try to access the X server. We cannot run those. Co-authored-by: Massimiliano Culpo <[email protected]>
Add version 1.20, fix including the glib-2.0 header files and add missing dependencies: libunwind and kmod.
* adios2: Fix compile errors for gcc 11 * unifyfs: Suppress bogus warnings for gcc 11 * conduit: Fix compile errors for gcc 11
This PR adds a "spack tags" command to output package tags or (available) packages with those tags. It also ensures each package is listed in the tag cache ONLY ONCE per tag.
* py-pylint: needs py-pip for build * alphabetize py- dependencies * add comment pointing to issue * fix style
Bumps [actions/checkout](https://github.com/actions/checkout) from 2.3.4 to 2.3.5. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@5a4ac90...1e204e9) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
The `--generic` argument allows printing the best generic target for the current machine. This can be quite handy when wanting to find the generic architecture to use when building a shared software stack for multiple machines.
- add version 6.0.5 - add patch to allow fsl to use newer gcc versions - add patch to allow fsl to use newer cuda versions - remove constraints on gcc and cuda versions - add filters to prevent using system headers and libraries - clean up the installed tree
- added more versions in case packages request a specific version of docbook-xml - added a "current" alias to handle when packages use that
spack#26538 introduced a typo that causes the Docker image build to fail.
gconf depends on gettext and libintl (dep: intltool) glibmm, gtkmm, libcanberra and cups need pkgconfig glibmm needs libsigc++ < 2.9x(which are 3.x pre-releases) libsigc++@:2.9 depends on m4 for the build Co-authored-by: Massimiliano Culpo <[email protected]>
Required for building [email protected] from source. However, the build is currently failing. As mentioned in the last commit, the gaussian package in the custom sdsc package repo likely needs some refactoring.
Successfully built as part of the pre-production expanse/0.17.3/cpu/a test instance currently deployed on Expanse. Waiting for testing. An amber@20 spec build script was also include here. Note, however, the build failed to deploy in the same instance. We may will revisit, if necessary. e.g., if requested by user after production deployment of the new instance.
Contributed by Jerry Greenberg @ SDSC
This is a modified version of the upstream spack/spack vasp package captured on this date from the project's develop branch. The major changes were to rename the package vasp6 --- in order allow different vasp group permissions between vasp6 and vasp5 on Expanse --- and add vasp v6.2.1.
Contributed by Jerry Greenberg @ SDSC
The aim here is to simplify the structure of the packages.yaml file. There are currently appears to be no advantages in specifying the supported architecture(s) when referring to external packages. However, we have observed Spack concretization and build issues when they are not specified correctly and/or maintained properly. Hence, this simplification to a non-architecture-specific definition of external packages in the packages.yaml file should eliminate these problems and, hopefully, not create any new ones.
Minor changes made to expanse/0.17.3/gpu during testing on devexp in preparation for production deployment. More specific changes like the deployment of [email protected] backend=multicore will again be noted prior to production deployment when the package depenency chains undergo a final adjustment.
Minor changes made to expanse/0.17.3/cpu during testing on devexp in preparation for production deployment. More specific changes like will be noted prior to production deployment when the package depenency chains undergo a final adjustment.
On systems like Expanse or TSSC, we rely on NVIDIA's Bright Cluster Manager to install a host OS and other software packages that will serve Spack as external packages. In this case, lmod is provided by Bright and is not needed (internally) for our Spack deployments on SDSC's HPC systems.
Here, we have attempted to simplify the modules.yaml configuration file prior to production deployment of the expanse/0.17.3/cpu Spack instance. The primary change is to eliminate as many package-specific suffixes entries that need to maintained over time by using generic, global sufixes where it makes sense. e.g., +openmp: omp
We are reorganzing the Spack package dependency chains one final time before completing the first production depolyments of expanse/0.17.3/cpu. One task as part of this effort is to remove all spec build scripts for packages that have a manual_download = True requirement from the dependency chains as they will need to be run manually as a separate process once the more automated builds have been successfully deployed.
Attempting to support Trinity within Spack will likely be quite difficult long-term. However, the developers already distribute Trinity via Singularity containers that they build and maintain [1]. We plan to provide support for Trinity on Expanse (and TSCC?) using these official containers. [1] https://data.broadinstitute.org/Trinity/TRINITY_SINGULARITY
…e/0.17.3/cpu We are reorganzing the Spack package dependency chains one final time before completing the first production depolyments of expanse/0.17.3/cpu. One task as part of this effort is to remove all spec build scripts for packages that have a manual_download = True requirement from the dependency chains as they will need to be run manually as a separate process once the more automated builds have been successfully deployed.
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 3.1.2 to 4.6.0. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@v3.1.2...57ded4d) --- updated-dependencies: - dependency-name: actions/setup-python dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
mkandes
force-pushed
the
sdsc-0.17.3
branch
from
7581e69
to
0cf7ba9
Compare
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.
Bumps actions/setup-python from 3.1.2 to 4.6.0.
Release notes
Sourced from actions/setup-python's releases.
... (truncated)
Commits
57ded4dupdate@azure/storage-blob(#655)df6abccupdate xml2js (#652)7a4f344Add warning for empty cache paths (#642)d1244c8Remove ubuntu-18.04 from e2e (#641)3091b37Fix glob bug in package.json scripts section (#637)dfa76f8Update configuration files (#622)03eb867Add error handling for saving and restoring cache (#618)b41aaf9Merge pull request #621 from akv-platform/reusable-workflow0ffa49cAdd update-config-files.ymlec365b4Add and configure ESLint and update configuration for Prettier (#617)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)