pivot and var_names incompatible in VariantFrequencies
#84
Workflow file for this run
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
| # Run this job on pushes to `main`, and for pull requests. If you don't specify | |
| # `branches: [main], then this actions runs _twice_ on pull requests, which is | |
| # annoying. | |
| name: CI | |
| on: | |
| push: | |
| branches: | |
| - main | |
| tags: | |
| # Version tags. | |
| # | |
| # Tags matching this pattern will cause the "release" job below to run, | |
| # so edit it carefully! It should not match arbitrary tags. | |
| - "[0-9]+.[0-9]+.[0-9]+*" | |
| pull_request: | |
| jobs: | |
| test-source: | |
| name: test-source ubuntu-latest | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: actions/checkout@v3 | |
| # If you wanted to use multiple Python versions, you'd have specify a matrix in the job and | |
| # reference the matrixe python version here. | |
| - uses: actions/setup-python@v3 | |
| with: | |
| python-version: 3.9 | |
| # Cache the installation of Poetry itself, e.g. the next step. This prevents the workflow | |
| # from installing Poetry every time, which can be slow. Note the use of the Poetry version | |
| # number in the cache key, and the "-0" suffix: this allows you to invalidate the cache | |
| # manually if/when you want to upgrade Poetry, or if something goes wrong. This could be | |
| # mildly cleaner by using an environment variable, but I don't really care. | |
| - name: cache poetry install | |
| uses: actions/cache@v3 | |
| with: | |
| path: ~/.local | |
| key: poetry-1.3.1-0 | |
| # Install Poetry. You could do this manually, or there are several actions that do this. | |
| # `snok/install-poetry` seems to be minimal yet complete, and really just calls out to | |
| # Poetry's default install script, which feels correct. I pin the Poetry version here | |
| # because Poetry does occasionally change APIs between versions and I don't want my | |
| # actions to break if it does. | |
| # | |
| # The key configuration value here is `virtualenvs-in-project: true`: this creates the | |
| # venv as a `.venv` in your testing directory, which allows the next step to easily | |
| # cache it. | |
| - uses: snok/install-poetry@v1 | |
| with: | |
| version: 1.3.1 | |
| virtualenvs-create: true | |
| virtualenvs-in-project: true | |
| # Cache your dependencies (i.e. all the stuff in your `pyproject.toml`). Note the cache | |
| # key: if you're using multiple Python versions, or multiple OSes, you'd need to include | |
| # them in the cache key. I'm not, so it can be simple and just depend on the poetry.lock. | |
| - name: cache deps | |
| id: cache-deps | |
| uses: actions/cache@v3 | |
| with: | |
| path: .venv | |
| key: pydeps-${{ hashFiles('**/poetry.lock') }} | |
| # Install dependencies. | |
| - run: poetry install --no-interaction --no-root | |
| if: steps.cache-deps.outputs.cache-hit != 'true' | |
| # Install project. | |
| - run: poetry install --no-interaction | |
| # Run tests. | |
| - run: poetry run pytest |