Skip the four known-broken tests in code instead of CI -skip flags

The go test -skip flag proved unreliable in the full-suite CI shape
(the same pattern skipped correctly in isolation but ran on the
runner), so each of the four tests now carries an explicit t.Skip with
the reason and a pointer to issue #9. The CI workflow drops the -skip
argument and keeps serial package execution.
This commit is contained in:
BaaRai
2026-10-10 18:12:42 +02:00
parent 78a2d2c01f
commit 525ad9ffde
5 changed files with 6 additions and 2 deletions
+2 -2
View File
@@ -37,13 +37,13 @@ jobs:
# fresh database.
# - TestSideUsageRecordedOnceOnConsumerCancellation: concurrency/cancellation
# test that passes locally but is timing-sensitive on 2-core CI runners.
# Skipping keeps the baseline green so real regressions stand out.
# They now skip themselves in code (t.Skip with a pointer to the issue).
- name: go test
# -p 1: package test suites share the single postgres service; running
# them in parallel makes packages delete each other's rows (observed
# as rotating failures in the agent package). Serial package execution
# keeps the database state deterministic.
run: go test -p 1 ./... -skip 'TestInterceptFilterHTTP|TestGraphOverviewExpansAssociatedCompanyScope|TestCaptureApprovalLifecycle|TestSideUsageRecordedOnceOnConsumerCancellation'
run: go test -p 1 ./...
web:
runs-on: ubuntu-latest