Skip to content

chore(deps)(deps-dev): bump pytest from 9.1.1 to 9.2.0 in the python-dependencies group across 1 directory #79

chore(deps)(deps-dev): bump pytest from 9.1.1 to 9.2.0 in the python-dependencies group across 1 directory

chore(deps)(deps-dev): bump pytest from 9.1.1 to 9.2.0 in the python-dependencies group across 1 directory #79

Workflow file for this run

name: Python CI
on:
push:
branches: [ "main" ]
pull_request:
branches: [ "main" ]
env:
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true
# The old job hand-listed eleven `python -m unittest` commands, which meant
# a new suite stayed unrun until someone remembered to add it (and
# tests/test_kde_wayland.py, tests/test_experimental_addons.py and
# .quarantine/tests never ran at all). Collecting `tests/` instead makes the
# suite self-listing; the two suites that need distro modules now skip
# themselves when those modules are missing, and a second job installs them
# from apt so they really run somewhere.
jobs:
test:
name: Unit tests (${{ matrix.python-version }})
runs-on: ubuntu-latest
strategy:
fail-fast: false
# Lowest and newest declared by pyproject.toml, plus the interpreter
# current stable distributions ship. A failure on 3.10/3.11 means the
# floor is a claim, not a fact. On 3.10 the pins resolve evdev 1.9.3
# instead of 2.0.0 (that release needs >=3.11), so this job is also
# the only one exercising the older API the distro packages ship.
matrix:
python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
steps:
- uses: actions/checkout@v4
- name: Set up Python ${{ matrix.python-version }}
uses: actions/setup-python@v5
with:
python-version: ${{ matrix.python-version }}
cache: pip
- name: Install dependencies
run: |
python -m pip install --upgrade pip
python -m pip install -r requirements-dev.txt
- name: Run unit tests with coverage
# --timeout comes from pytest-timeout: a test that waits on a
# thread must fail the run instead of burning the job's 6h limit.
run: >
python -m pytest tests -q --timeout=120
--cov=src --cov=tools --cov-report=term-missing
--cov-report=xml
- name: Upload coverage
if: matrix.python-version == '3.12'
uses: actions/upload-artifact@v4
with:
name: coverage-xml
path: coverage.xml
- name: Check the unittest entry point still works
# README documents `python -m unittest discover` as the no-pytest
# path; prove it instead of assuming the two runners diverge.
run: python -m unittest discover -s tests -t . -q
distro-bindings:
name: Suite with distro D-Bus and GObject bindings
runs-on: ubuntu-24.04
steps:
- uses: actions/checkout@v4
# python3-dbus and python3-gi bind to the interpreter that ships
# them, so this job uses the runner's own python3 (3.12 on
# ubuntu-24.04) in a venv that can see the system modules. It is the
# only job where the KDE Wayland driver's suite actually runs.
#
# python3-tk is not optional here: the distro CPython build has no
# _tkinter, so `import customtkinter` dies at collection and pytest
# reports it as a missing core dependency. The matrix jobs do not see
# this because actions/setup-python's interpreters are built with Tk.
#
# python3-pil.imagetk is the same kind of surprise: the distro splits
# PIL.ImageTk out of python3-pil, so experimental/color_spin/app.py
# raised "cannot import name 'ImageTk' from PIL" only on this runner.
- name: Install the system bindings the app cannot pip-install
run: |
sudo apt-get update
sudo apt-get install -y --no-install-recommends \
python3 python3-venv python3-tk python3-dbus python3-gi \
gir1.2-glib-2.0 python3-numpy python3-pil python3-pil.imagetk
- name: Build a venv that can see them
run: |
python3 -m venv --system-site-packages .venv
.venv/bin/pip install --upgrade pip
.venv/bin/pip install -r requirements-dev.txt
- name: Run the full suite
# fail_if_no_tests is the guard: if the skip logic hid a whole
# suite, the job must not pass on an empty run.
run: >
.venv/bin/python -m pytest tests -q --timeout=120
--cov=src --cov-report=term-missing
# Every AppImage defect found so far was discovered by pushing a tag: the
# artifact path (v3.5.0), meson and patchelf outside PATH plus the wrong
# wheel version (v3.5.1), and a -dev package the apt list did not name.
# Two releases shipped without the download while each surprise cost a
# separate attempt. The local build cannot see any of them --
# build/appimage/wheels still holds the output of an older bootstrap, and
# the build loop skips pip wheel for anything already cached. This job is
# the clean runner, on every push, and publishes nothing.
appimage:
name: AppImage build (clean runner)
runs-on: ubuntu-latest
timeout-minutes: 60
steps:
- uses: actions/checkout@v4
- name: Install build dependencies
# Single source of truth, shared with the release workflow: if a
# module build.sh preflights has no package here, the guard suite
# fails before this job is even written.
run: bash tools/appimage/install-build-deps.sh
- name: Build the AppImage
# Ends with the smoke guard: the bundled interpreter imports every
# driver and the gi/dbus stack from the freshly built AppImage, so a
# wheel that packed no compiled extension fails here rather than on
# a user's machine.
run: ./tools/appimage/build.sh
- name: Verify the artifact exists
# Same path the release job attaches from.
run: |
test -s build/appimage/dist/LinuxTask-x86_64.AppImage
ls -l build/appimage/dist/LinuxTask-x86_64.AppImage
lint:
name: Lint (ruff)
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: "3.12"
cache: pip
- name: Install ruff
run: python -m pip install -r requirements-dev.txt
- name: Check
# Rules and their exemptions live in pyproject.toml. `ruff format`
# is deliberately not gating: the repository predates it and the
# one-shot reformat would touch 38 files (3958 diff lines), which
# belongs in its own commit, not in every feature branch.
run: python -m ruff check .