ldraney/landscaping-assistant
1
0
Fork 0
Code Issues 32 Pull requests 1 Projects Releases Packages Wiki Activity Actions 4

CI system tests fail: Chromium process timeout too low #58

New issue
Closed
opened 2026-06-02 12:45:06 +00:00 by ldraney · 0 comments
ldraney commented 2026-06-02 12:45:06 +00:00
Owner
Copy link

Type

Bug

Lineage

Standalone — discovered in pipeline #128 after PR #56 merge.

Repo

ldraney/landscaping-assistant

What Broke

All 7 system tests fail with Ferrum::ProcessTimeoutError: Browser did not produce websocket url within 10 seconds. Pipeline can't reach build-and-push step, blocking prod deployment.

Repro Steps

  1. Merge any PR to main
  2. Pipeline runs all 89 specs
  3. System tests fail when Chromium can't boot in time on single-worker pod

Expected Behavior

System tests should pass — Chromium should get enough time to start in a resource-constrained CI environment.

Environment

  • Woodpecker CI, single worker pod
  • Cuprite 0.17 / Ferrum 0.17.2
  • Chromium headless in CI container

File Targets

  • spec/support/system_test_config.rb -- increase process_timeout to 30s, timeout to 15s

Acceptance Criteria

  • System tests pass in CI
  • Pipeline succeeds through build-and-push

Constraints

  • Don't change test logic, only timeout values

Checklist

  • PR opened
  • Tests pass

Related

  • landscaping-assistant -- project
### Type Bug ### Lineage Standalone — discovered in pipeline #128 after PR #56 merge. ### Repo `ldraney/landscaping-assistant` ### What Broke All 7 system tests fail with `Ferrum::ProcessTimeoutError: Browser did not produce websocket url within 10 seconds`. Pipeline can't reach build-and-push step, blocking prod deployment. ### Repro Steps 1. Merge any PR to main 2. Pipeline runs all 89 specs 3. System tests fail when Chromium can't boot in time on single-worker pod ### Expected Behavior System tests should pass — Chromium should get enough time to start in a resource-constrained CI environment. ### Environment - Woodpecker CI, single worker pod - Cuprite 0.17 / Ferrum 0.17.2 - Chromium headless in CI container ### File Targets - `spec/support/system_test_config.rb` -- increase process_timeout to 30s, timeout to 15s ### Acceptance Criteria - [ ] System tests pass in CI - [ ] Pipeline succeeds through build-and-push ### Constraints - Don't change test logic, only timeout values ### Checklist - [ ] PR opened - [ ] Tests pass ### Related - `landscaping-assistant` -- project
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
docs/update-app-architecture
revert-213
move-other-crew-bottom-remove-schedule
feature/today-view-improvements
154-enable-assume-ssl
revert-145-person-icon
docs/user-stories-auth
docs/update-infra-pipeline-post-incident
fix-cache-step-blocking-deploy
fix-kaniko-registry-pull
deactivate-from-today
feature/quick-address-entry
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ldraney/landscaping-assistant#58
No description provided.