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
|
|
|
name: windows
|
2022-01-25 22:29:17 +00:00
|
|
|
|
|
|
|
on:
|
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
|
|
|
workflow_call:
|
2022-06-08 22:46:46 +00:00
|
|
|
|
|
|
|
concurrency:
|
2022-09-07 18:12:57 +00:00
|
|
|
group: windows-${{github.ref}}-${{github.event.pull_request.number || github.run_number}}
|
2022-06-08 22:46:46 +00:00
|
|
|
cancel-in-progress: true
|
|
|
|
|
2022-01-25 22:29:17 +00:00
|
|
|
defaults:
|
|
|
|
run:
|
|
|
|
shell:
|
|
|
|
powershell Invoke-Expression -Command ".\share\spack\qa\windows_test_setup.ps1"; {0}
|
|
|
|
jobs:
|
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
|
|
|
unit-tests:
|
2022-01-25 22:29:17 +00:00
|
|
|
runs-on: windows-latest
|
|
|
|
steps:
|
2022-04-27 11:47:50 +00:00
|
|
|
- uses: actions/checkout@2541b1294d2704b0964813337f33b291d3f8596b
|
2022-01-25 22:29:17 +00:00
|
|
|
with:
|
|
|
|
fetch-depth: 0
|
2022-08-03 07:08:03 +00:00
|
|
|
- uses: actions/setup-python@b55428b1882923874294fa556849718a1d7f2ca5
|
2022-01-25 22:29:17 +00:00
|
|
|
with:
|
|
|
|
python-version: 3.9
|
|
|
|
- name: Install Python packages
|
|
|
|
run: |
|
2022-09-16 12:38:29 +00:00
|
|
|
python -m pip install --upgrade pip six pywin32 setuptools codecov pytest-cov
|
2022-01-25 22:29:17 +00:00
|
|
|
- name: Create local develop
|
|
|
|
run: |
|
|
|
|
.\spack\.github\workflows\setup_git.ps1
|
|
|
|
- name: Unit Test
|
|
|
|
run: |
|
|
|
|
echo F|xcopy .\spack\share\spack\qa\configuration\windows_config.yaml $env:USERPROFILE\.spack\windows\config.yaml
|
2022-09-16 12:38:29 +00:00
|
|
|
cd spack
|
|
|
|
dir
|
|
|
|
(Get-Item '.\lib\spack\docs\_spack_root').Delete()
|
|
|
|
spack unit-test --verbose --cov --cov-config=pyproject.toml --ignore=lib/spack/spack/test/cmd
|
|
|
|
coverage combine -a
|
|
|
|
coverage xml
|
2022-09-20 12:03:47 +00:00
|
|
|
- uses: codecov/codecov-action@d9f34f8cd5cb3b3eb79b3e4b5dae3a16df499a70
|
2022-09-16 12:38:29 +00:00
|
|
|
with:
|
|
|
|
flags: unittests,windows
|
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
|
|
|
unit-tests-cmd:
|
2022-01-25 22:29:17 +00:00
|
|
|
runs-on: windows-latest
|
|
|
|
steps:
|
2022-04-27 11:47:50 +00:00
|
|
|
- uses: actions/checkout@2541b1294d2704b0964813337f33b291d3f8596b
|
2022-01-25 22:29:17 +00:00
|
|
|
with:
|
|
|
|
fetch-depth: 0
|
2022-08-03 07:08:03 +00:00
|
|
|
- uses: actions/setup-python@b55428b1882923874294fa556849718a1d7f2ca5
|
2022-01-25 22:29:17 +00:00
|
|
|
with:
|
|
|
|
python-version: 3.9
|
|
|
|
- name: Install Python packages
|
|
|
|
run: |
|
2022-09-16 12:38:29 +00:00
|
|
|
python -m pip install --upgrade pip six pywin32 setuptools codecov coverage pytest-cov
|
2022-01-25 22:29:17 +00:00
|
|
|
- name: Create local develop
|
|
|
|
run: |
|
|
|
|
.\spack\.github\workflows\setup_git.ps1
|
|
|
|
- name: Command Unit Test
|
|
|
|
run: |
|
|
|
|
echo F|xcopy .\spack\share\spack\qa\configuration\windows_config.yaml $env:USERPROFILE\.spack\windows\config.yaml
|
2022-09-16 12:38:29 +00:00
|
|
|
cd spack
|
|
|
|
(Get-Item '.\lib\spack\docs\_spack_root').Delete()
|
|
|
|
spack unit-test --verbose --cov --cov-config=pyproject.toml lib/spack/spack/test/cmd
|
|
|
|
coverage combine -a
|
|
|
|
coverage xml
|
2022-09-20 12:03:47 +00:00
|
|
|
- uses: codecov/codecov-action@d9f34f8cd5cb3b3eb79b3e4b5dae3a16df499a70
|
2022-09-16 12:38:29 +00:00
|
|
|
with:
|
|
|
|
flags: unittests,windows
|
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
|
|
|
build-abseil:
|
2022-01-25 22:29:17 +00:00
|
|
|
runs-on: windows-latest
|
|
|
|
steps:
|
2022-04-27 11:47:50 +00:00
|
|
|
- uses: actions/checkout@2541b1294d2704b0964813337f33b291d3f8596b
|
2022-01-25 22:29:17 +00:00
|
|
|
with:
|
|
|
|
fetch-depth: 0
|
2022-08-03 07:08:03 +00:00
|
|
|
- uses: actions/setup-python@b55428b1882923874294fa556849718a1d7f2ca5
|
2022-01-25 22:29:17 +00:00
|
|
|
with:
|
|
|
|
python-version: 3.9
|
|
|
|
- name: Install Python packages
|
|
|
|
run: |
|
|
|
|
python -m pip install --upgrade pip six pywin32 setuptools codecov coverage
|
|
|
|
- name: Build Test
|
|
|
|
run: |
|
|
|
|
spack compiler find
|
|
|
|
echo F|xcopy .\spack\share\spack\qa\configuration\windows_config.yaml $env:USERPROFILE\.spack\windows\config.yaml
|
|
|
|
spack external find cmake
|
|
|
|
spack external find ninja
|
|
|
|
spack install abseil-cpp
|
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
|
|
|
make-installer:
|
2022-01-25 22:29:17 +00:00
|
|
|
runs-on: windows-latest
|
|
|
|
steps:
|
|
|
|
- name: Disable Windows Symlinks
|
|
|
|
run: |
|
|
|
|
git config --global core.symlinks false
|
|
|
|
shell:
|
|
|
|
powershell
|
2022-04-27 11:47:50 +00:00
|
|
|
- uses: actions/checkout@2541b1294d2704b0964813337f33b291d3f8596b
|
2022-01-25 22:29:17 +00:00
|
|
|
with:
|
|
|
|
fetch-depth: 0
|
2022-08-03 07:08:03 +00:00
|
|
|
- uses: actions/setup-python@b55428b1882923874294fa556849718a1d7f2ca5
|
2022-01-25 22:29:17 +00:00
|
|
|
with:
|
|
|
|
python-version: 3.9
|
|
|
|
- name: Install Python packages
|
|
|
|
run: |
|
2022-09-16 12:38:29 +00:00
|
|
|
python -m pip install --upgrade pip six pywin32 setuptools
|
2022-01-25 22:29:17 +00:00
|
|
|
- name: Add Light and Candle to Path
|
|
|
|
run: |
|
|
|
|
$env:WIX >> $GITHUB_PATH
|
|
|
|
- name: Run Installer
|
|
|
|
run: |
|
|
|
|
.\spack\share\spack\qa\setup_spack.ps1
|
|
|
|
spack make-installer -s spack -g SILENT pkg
|
|
|
|
echo "installer_root=$((pwd).Path)" | Out-File -FilePath $Env:GITHUB_ENV -Encoding utf8 -Append
|
|
|
|
env:
|
|
|
|
ProgressPreference: SilentlyContinue
|
2022-05-21 06:57:19 +00:00
|
|
|
- uses: actions/upload-artifact@3cea5372237819ed00197afe530f5a7ea3e805c8
|
2022-01-25 22:29:17 +00:00
|
|
|
with:
|
|
|
|
name: Windows Spack Installer Bundle
|
|
|
|
path: ${{ env.installer_root }}\pkg\Spack.exe
|
2022-05-21 06:57:19 +00:00
|
|
|
- uses: actions/upload-artifact@3cea5372237819ed00197afe530f5a7ea3e805c8
|
2022-01-25 22:29:17 +00:00
|
|
|
with:
|
|
|
|
name: Windows Spack Installer
|
|
|
|
path: ${{ env.installer_root}}\pkg\Spack.msi
|
|
|
|
execute-installer:
|
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
|
|
|
needs: make-installer
|
2022-01-25 22:29:17 +00:00
|
|
|
runs-on: windows-latest
|
|
|
|
defaults:
|
|
|
|
run:
|
|
|
|
shell: pwsh
|
|
|
|
steps:
|
2022-08-03 07:08:03 +00:00
|
|
|
- uses: actions/setup-python@b55428b1882923874294fa556849718a1d7f2ca5
|
2022-01-25 22:29:17 +00:00
|
|
|
with:
|
|
|
|
python-version: 3.9
|
|
|
|
- name: Install Python packages
|
|
|
|
run: |
|
2022-09-16 12:38:29 +00:00
|
|
|
python -m pip install --upgrade pip six pywin32 setuptools
|
2022-01-25 22:29:17 +00:00
|
|
|
- name: Setup installer directory
|
|
|
|
run: |
|
|
|
|
mkdir -p spack_installer
|
|
|
|
echo "spack_installer=$((pwd).Path)\spack_installer" | Out-File -FilePath $Env:GITHUB_ENV -Encoding utf8 -Append
|
2022-04-11 07:55:32 +00:00
|
|
|
- uses: actions/download-artifact@v3
|
2022-01-25 22:29:17 +00:00
|
|
|
with:
|
|
|
|
name: Windows Spack Installer Bundle
|
|
|
|
path: ${{ env.spack_installer }}
|
|
|
|
- name: Execute Bundled Installer
|
|
|
|
run: |
|
|
|
|
$proc = Start-Process ${{ env.spack_installer }}\spack.exe "/install /quiet" -Passthru
|
|
|
|
$handle = $proc.Handle # cache proc.Handle
|
|
|
|
$proc.WaitForExit();
|
|
|
|
$LASTEXITCODE
|
|
|
|
env:
|
|
|
|
ProgressPreference: SilentlyContinue
|
2022-04-11 07:55:32 +00:00
|
|
|
- uses: actions/download-artifact@v3
|
2022-01-25 22:29:17 +00:00
|
|
|
with:
|
|
|
|
name: Windows Spack Installer
|
|
|
|
path: ${{ env.spack_installer }}
|
|
|
|
- name: Execute MSI
|
|
|
|
run: |
|
|
|
|
$proc = Start-Process ${{ env.spack_installer }}\spack.msi "/quiet" -Passthru
|
|
|
|
$handle = $proc.Handle # cache proc.Handle
|
|
|
|
$proc.WaitForExit();
|
2021-07-06 04:43:52 +00:00
|
|
|
$LASTEXITCODE
|