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

Fix CI system tests: set FERRUM_PROCESS_TIMEOUT env var #61

Merged
ldraney merged 2 commits from fix/ci-ferrum-env-timeout into main 2026-06-02 20:46:37 +00:00
Conversation 0 Commits 2 Files changed 2 +3 -2
ldraney commented 2026-06-02 20:37:55 +00:00
Owner
Copy link

Summary

  • Add FERRUM_PROCESS_TIMEOUT=30 to the test step in .woodpecker.yaml
  • Root cause: Ferrum reads its process timeout from env var with a 10s default, ignoring the Ruby option passed through Cuprite during reset! calls

Changes

  • .woodpecker.yaml -- added FERRUM_PROCESS_TIMEOUT env var to test step

Test Plan

  • All 89 specs pass in CI including 7 system tests
  • Pipeline reaches build-and-push step

Review Checklist

  • No secrets committed
  • No unnecessary file changes
  • Commit messages are descriptive

Related Notes

  • Closes #58
  • landscaping-assistant -- project
## Summary - Add `FERRUM_PROCESS_TIMEOUT=30` to the test step in `.woodpecker.yaml` - Root cause: Ferrum reads its process timeout from env var with a 10s default, ignoring the Ruby option passed through Cuprite during `reset!` calls ## Changes - `.woodpecker.yaml` -- added FERRUM_PROCESS_TIMEOUT env var to test step ## Test Plan - [ ] All 89 specs pass in CI including 7 system tests - [ ] Pipeline reaches build-and-push step ## Review Checklist - [ ] No secrets committed - [ ] No unnecessary file changes - [ ] Commit messages are descriptive ## Related Notes - Closes #58 - `landscaping-assistant` -- project
Increase Chromium process_timeout for CI system tests
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
Details
ci/woodpecker/pr/woodpecker Pipeline failed
Details
CI / scan_ruby (pull_request) Has been cancelled
Details
CI / scan_js (pull_request) Has been cancelled
Details
CI / lint (pull_request) Has been cancelled
Details
f79ec123fd 
Ferrum::ProcessTimeoutError in CI — single-worker pod can't boot
Chromium within 10s under load. Bump process_timeout to 30s and
timeout to 15s.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Fix CI system tests: set FERRUM_PROCESS_TIMEOUT env var
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
Details
ci/woodpecker/pr/woodpecker Pipeline failed
Details
CI / scan_ruby (pull_request) Has been cancelled
Details
CI / scan_js (pull_request) Has been cancelled
Details
CI / lint (pull_request) Has been cancelled
Details
6f8dbb6f4b 
The process_timeout Ruby option wasn't reaching Ferrum during
Capybara reset! calls. Ferrum reads FERRUM_PROCESS_TIMEOUT env var
directly with a 10s default — set it to 30s in the CI environment.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
ldraney deleted branch fix/ci-ferrum-env-timeout 2026-06-02 20:46:37 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
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!61
No description provided.