Skip to content

SEP-1909: Decide where ty enforcement runs and how it scopes #10202

SEP-1909: Decide where ty enforcement runs and how it scopes

SEP-1909: Decide where ty enforcement runs and how it scopes #10202

Re-run triggered September 3, 2026 22:29
Status Failure
Total duration 5m 34s
Artifacts 1

ci.yml

on: pull_request
label-gate
2s
label-gate
changes
6s
changes
precommit-light
12s
precommit-light
Matrix: python / bandit
Matrix: python / build
Matrix: python / check_migrations
Matrix: python / lock_check
Matrix: python / test
precommit-python
46s
precommit-python
precommit-frontend
0s
precommit-frontend
python  /  test (postgres)
2m 31s
python / test (postgres)
build
1m 6s
build
pipeline-syntax
0s
pipeline-syntax
frontend  /  Build & Storybook
frontend / Build & Storybook
frontend  /  Unit tests (Vitest)
frontend / Unit tests (Vitest)
frontend  /  Lint & typecheck
frontend / Lint & typecheck
frontend  /  ...  /  Chromium)
frontend / E2E (Playwright / Chromium)
ci-success
3s
ci-success
Fit to window
Zoom out
Zoom in

Annotations

6 errors
python / test (3.12.3)
Process completed with exit code 2.
python / test (3.11.9)
The strategy configuration was canceled because "python.test.ubuntu-latest_3_12_3" failed
python / test (3.11.9)
The operation was canceled.
python / test (3.13)
The strategy configuration was canceled because "python.test.ubuntu-latest_3_12_3" failed
python / test (3.13)
The operation was canceled.
ci-success
Process completed with exit code 1.

Artifacts

Produced during runtime
Name Size Digest
percona~SEP~JHOFPK.dockerbuild
35.7 KB
sha256:de3236ba2219ada0ce17c1f76342cd8973fa17bbd159f32580d593af0985488e