2020-05-09 20:35:14 +00:00
|
|
|
name: macos tests
|
|
|
|
|
|
|
|
|
|
on:
|
|
|
|
|
push:
|
|
|
|
|
branches:
|
|
|
|
|
- develop
|
2020-06-30 23:10:10 +00:00
|
|
|
- releases/**
|
2020-05-09 20:35:14 +00:00
|
|
|
pull_request:
|
|
|
|
|
branches:
|
|
|
|
|
- develop
|
2020-07-04 06:52:11 +00:00
|
|
|
- releases/**
|
2020-05-09 20:35:14 +00:00
|
|
|
jobs:
|
|
|
|
|
build:
|
|
|
|
|
runs-on: macos-latest
|
2020-11-12 20:26:23 +00:00
|
|
|
strategy:
|
|
|
|
|
matrix:
|
2020-11-12 21:22:41 +00:00
|
|
|
python-version: [3.8]
|
2020-05-09 20:35:14 +00:00
|
|
|
steps:
|
|
|
|
|
- uses: actions/checkout@v2
|
2020-07-28 16:04:52 +00:00
|
|
|
with:
|
|
|
|
|
fetch-depth: 0
|
2020-07-28 13:31:22 +00:00
|
|
|
- uses: actions/setup-python@v2
|
2020-05-09 20:35:14 +00:00
|
|
|
with:
|
2020-11-12 20:26:23 +00:00
|
|
|
python-version: ${{ matrix.python-version }}
|
2020-05-09 20:35:14 +00:00
|
|
|
- name: Install Python packages
|
|
|
|
|
run: |
|
|
|
|
|
pip install --upgrade pip six setuptools
|
2020-06-15 18:24:56 +00:00
|
|
|
pip install --upgrade codecov coverage
|
add mypy to style checks; rename `spack flake8` to `spack style` (#20384)
I lost my mind a bit after getting the completion stuff working and
decided to get Mypy working for spack as well. This adds a
`.mypy.ini` that checks all of the spack and llnl modules, though
not yet packages, and fixes all of the identified missing types and
type issues for the spack library.
In addition to these changes, this includes:
* rename `spack flake8` to `spack style`
Aliases flake8 to style, and just runs flake8 as before, but with
a warning. The style command runs both `flake8` and `mypy`,
in sequence. Added --no-<tool> options to turn off one or the
other, they are on by default. Fixed two issues caught by the tools.
* stub typing module for python2.x
We don't support typing in Spack for python 2.x. To allow 2.x to
support `import typing` and `from typing import ...` without a
try/except dance to support old versions, this adds a stub module
*just* for python 2.x. Doing it this way means we can only reliably
use all type hints in python3.7+, and mypi.ini has been updated to
reflect that.
* add non-default black check to spack style
This is a first step to requiring black. It doesn't enforce it by
default, but it will check it if requested. Currently enforcing the
line length of 79 since that's what flake8 requires, but it's a bit odd
for a black formatted project to be quite that narrow. All settings are
in the style command since spack has no pyproject.toml and I don't
want to add one until more discussion happens. Also re-format
`style.py` since it no longer passed the black style check
with the new length.
* use style check in github action
Update the style and docs action to use `spack style`, adding in mypy
and black to the action even if it isn't running black right now.
2020-12-23 05:39:10 +00:00
|
|
|
pip install --upgrade flake8 pep8-naming mypy
|
2020-05-09 20:35:14 +00:00
|
|
|
- name: Setup Homebrew packages
|
|
|
|
|
run: |
|
2020-10-24 01:54:34 +00:00
|
|
|
brew install dash fish gcc gnupg2 kcov
|
2020-05-09 20:35:14 +00:00
|
|
|
- name: Run unit tests
|
|
|
|
|
run: |
|
|
|
|
|
git --version
|
2020-07-28 16:04:52 +00:00
|
|
|
. .github/workflows/setup_git.sh
|
2020-05-09 20:35:14 +00:00
|
|
|
. share/spack/setup-env.sh
|
spack test (#15702)
Users can add test() methods to their packages to run smoke tests on
installations with the new `spack test` command (the old `spack test` is
now `spack unit-test`). spack test is environment-aware, so you can
`spack install` an environment and then run `spack test run` to run smoke
tests on all of its packages. Historical test logs can be perused with
`spack test results`. Generic smoke tests for MPI implementations, C,
C++, and Fortran compilers as well as specific smoke tests for 18
packages.
Inside the test method, individual tests can be run separately (and
continue to run best-effort after a test failure) using the `run_test`
method. The `run_test` method encapsulates finding test executables,
running and checking return codes, checking output, and error handling.
This handles the following trickier aspects of testing with direct
support in Spack's package API:
- [x] Caching source or intermediate build files at build time for
use at test time.
- [x] Test dependencies,
- [x] packages that require a compiler for testing (such as library only
packages).
See the packaging guide for more details on using Spack testing support.
Included is support for package.py files for virtual packages. This does
not change the Spack interface, but is a major change in internals.
Co-authored-by: Tamara Dahlgren <dahlgren1@llnl.gov>
Co-authored-by: wspear <wjspear@gmail.com>
Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2020-11-18 10:39:02 +00:00
|
|
|
coverage run $(which spack) unit-test
|
2020-05-09 20:35:14 +00:00
|
|
|
coverage combine
|
|
|
|
|
coverage xml
|
2020-07-29 08:18:20 +00:00
|
|
|
- uses: codecov/codecov-action@v1
|
2020-05-09 20:35:14 +00:00
|
|
|
with:
|
|
|
|
|
file: ./coverage.xml
|
|
|
|
|
flags: unittests,macos
|