fix(ci): increase quick test job timeout to 15 minutes for CI runner headroom
Co-authored-by: christianlouis <361235+christianlouis@users.noreply.github.com>
This commit is contained in:
@@ -115,7 +115,7 @@ jobs:
|
||||
test-quick:
|
||||
name: Quick Tests
|
||||
runs-on: ubuntu-latest
|
||||
timeout-minutes: 10
|
||||
timeout-minutes: 15
|
||||
needs: [lint, html-lint, dependency-scan]
|
||||
services:
|
||||
redis:
|
||||
|
||||
+1
-1
@@ -35,7 +35,7 @@ The pipeline follows a **fail-early** strategy: fast linters and quick tests run
|
||||
|
||||
### Quick Tests (`test-quick`)
|
||||
|
||||
- **Timeout:** 10 minutes (job), 120 seconds (per test via `pytest-timeout`)
|
||||
- **Timeout:** 15 minutes (job), 120 seconds (per test via `pytest-timeout`)
|
||||
- Runs the majority of tests (~2,790 unit + basic integration tests)
|
||||
- Excludes tests marked `e2e`, `requires_docker`, `requires_external`, or `slow`
|
||||
- Uses a Redis service container for tests that need it
|
||||
|
||||
@@ -368,7 +368,7 @@ The DocuElevate CI pipeline (`.github/workflows/ci.yml`) uses a **two-stage test
|
||||
2. **Integration Tests** (`test-integration`) — Runs ~28 Docker-based and external service tests. Only starts after quick tests pass. Uses testcontainers for WebDAV, OAuth, etc.
|
||||
|
||||
Both stages use `pytest-timeout` to prevent individual tests from hanging:
|
||||
- Quick tests: 120 seconds per test, 10-minute job timeout
|
||||
- Quick tests: 120 seconds per test, 15-minute job timeout
|
||||
- Integration tests: 300 seconds per test, 20-minute job timeout
|
||||
|
||||
```yaml
|
||||
|
||||
Reference in New Issue
Block a user