spack/.github/workflows/bootstrap-test.sh

#!/bin/bash
set -e
source share/spack/setup-env.sh
$PYTHON bin/spack bootstrap disable github-actions-v0.4
$PYTHON bin/spack bootstrap disable spack-install
$PYTHON bin/spack $SPACK_FLAGS solve zlib
tree $BOOTSTRAP/store
exit 0
Reorder workflow execution in GHA (#32183) This patchset refactors our GitHub actions into a single top-level ci workflow that invokes a series of reusable actions. The main goal of this is to be able to easily control which tests run and in what order based on the success or failure of top-level prechecks. Our previous workflows ran in three sets: * nix tests: style and verification first, then linux and macos tests if successful * windows tests: style and verification first, then linux and macos tests if successful * bootstrap tests As a result, the bootstrap tests ran even if the style failed, and style and verification had to run on two different platforms despite running identical checks. I'm relatively sure that's because of the limitation on dependencies between steps in the jobs. Reusable workflows allow us to run the style, verification and now audit checks once, then depending on the results, and the files changed, run the appropriate nix, windows and bootstrap tests. While it saves only a few minutes by itself, this makes it easier to refactor checks to subset tests without having to replicate tests or other workflow components in the future. Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com> 2022-09-02 21:09:23 +00:00			`#!/bin/bash`
Maintenance for the "bootstrap" workflow in CI (#44031) Removed a lot of duplication. Fixed an issue in containers, leading to false negative 2024-05-07 06:49:53 +00:00			`set -e`
Reorder workflow execution in GHA (#32183) This patchset refactors our GitHub actions into a single top-level ci workflow that invokes a series of reusable actions. The main goal of this is to be able to easily control which tests run and in what order based on the success or failure of top-level prechecks. Our previous workflows ran in three sets: * nix tests: style and verification first, then linux and macos tests if successful * windows tests: style and verification first, then linux and macos tests if successful * bootstrap tests As a result, the bootstrap tests ran even if the style failed, and style and verification had to run on two different platforms despite running identical checks. I'm relatively sure that's because of the limitation on dependencies between steps in the jobs. Reusable workflows allow us to run the style, verification and now audit checks once, then depending on the results, and the files changed, run the appropriate nix, windows and bootstrap tests. While it saves only a few minutes by itself, this makes it easier to refactor checks to subset tests without having to replicate tests or other workflow components in the future. Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com> 2022-09-02 21:09:23 +00:00			`source share/spack/setup-env.sh`
Maintenance for the "bootstrap" workflow in CI (#44031) Removed a lot of duplication. Fixed an issue in containers, leading to false negative 2024-05-07 06:49:53 +00:00			`$PYTHON bin/spack bootstrap disable github-actions-v0.4`
Deprecate spack bootstrap trust/untrust (#33600) * Deprecate spack bootstrap trust/untrust * Update CI * Update tests 2022-10-29 19:24:26 +00:00			`$PYTHON bin/spack bootstrap disable spack-install`
Maintenance for the "bootstrap" workflow in CI (#44031) Removed a lot of duplication. Fixed an issue in containers, leading to false negative 2024-05-07 06:49:53 +00:00			`$PYTHON bin/spack $SPACK_FLAGS solve zlib`
Reorder workflow execution in GHA (#32183) This patchset refactors our GitHub actions into a single top-level ci workflow that invokes a series of reusable actions. The main goal of this is to be able to easily control which tests run and in what order based on the success or failure of top-level prechecks. Our previous workflows ran in three sets: * nix tests: style and verification first, then linux and macos tests if successful * windows tests: style and verification first, then linux and macos tests if successful * bootstrap tests As a result, the bootstrap tests ran even if the style failed, and style and verification had to run on two different platforms despite running identical checks. I'm relatively sure that's because of the limitation on dependencies between steps in the jobs. Reusable workflows allow us to run the style, verification and now audit checks once, then depending on the results, and the files changed, run the appropriate nix, windows and bootstrap tests. While it saves only a few minutes by itself, this makes it easier to refactor checks to subset tests without having to replicate tests or other workflow components in the future. Co-authored-by: Massimiliano Culpo <massimiliano.culpo@gmail.com> 2022-09-02 21:09:23 +00:00			`tree $BOOTSTRAP/store`
			`exit 0`