mirror of
https://github.com/kuhyx/utils.git
synced 2026-11-10 22:47:14 +01:00
Some checks failed
crdt-sync pre-commit / pre-commit (push) Waiting to run
crdt-sync tests / test (3.10) (push) Waiting to run
crdt-sync tests / test (3.11) (push) Waiting to run
crdt-sync tests / test (3.12) (push) Waiting to run
gatelock pre-commit / pre-commit (push) Has been cancelled
gatelock tests / test (3.10) (push) Has been cancelled
gatelock tests / test (3.11) (push) Has been cancelled
gatelock tests / test (3.12) (push) Has been cancelled
The display fix in 161eccd could never prove itself: both workflows trigger
on `paths: ['gatelock/**']`, and the workflow files live under .github/, so
editing one changes nothing GitHub will act on. The tests job stayed red at
the last gatelock commit with the fix already pushed -- which is the worst
kind of green-looking red, because nothing was running to say otherwise.
A workflow is part of what it tests, so each now lists its own path.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BsXnTHyuuCUZsqetTaajcF
44 lines
1.4 KiB
YAML
44 lines
1.4 KiB
YAML
name: gatelock tests
|
|
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
# The workflow's own file counts as gatelock: editing only this file used
|
|
# to trigger nothing, so a fix to the job itself could never prove itself.
|
|
paths: ['gatelock/**', '.github/workflows/gatelock-tests.yml']
|
|
pull_request:
|
|
branches: [main]
|
|
paths: ['gatelock/**', '.github/workflows/gatelock-tests.yml']
|
|
|
|
jobs:
|
|
test:
|
|
runs-on: ubuntu-latest
|
|
defaults:
|
|
run:
|
|
working-directory: gatelock
|
|
strategy:
|
|
matrix:
|
|
python-version: ["3.10", "3.11", "3.12"]
|
|
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
|
|
- name: Set up Python ${{ matrix.python-version }}
|
|
uses: actions/setup-python@v5
|
|
with:
|
|
python-version: ${{ matrix.python-version }}
|
|
|
|
- name: Install dependencies
|
|
run: pip install -r requirements.txt
|
|
|
|
# The viewport, fit-check and keyboard tests drive real Tk: focus
|
|
# delivery, canvas scrolling and widget heights are Tk's own behaviour,
|
|
# and mocking them is what let a viewport that scrolled itself pass
|
|
# every check for a week. Headless they skip, silently taking coverage
|
|
# with them -- so the runner gets a display instead.
|
|
- name: Install a virtual X display
|
|
run: sudo apt-get update && sudo apt-get install -y xvfb
|
|
|
|
- name: Run tests with coverage
|
|
run: xvfb-run -a -s "-screen 0 1600x1200x24" python -m pytest -v
|