Fixes CI test timeouts on the arm64 runner
The first render with axe takes up to 7 s on the Raspberry Pi runner, above Vitest's 5 s default; the suite now allows 20 s per test. Also silences the router warning in the test that crashes a page on purpose, and makes the nginx test config return 404 instead of a redirect loop (500) while the test folder is still empty. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -618,3 +618,39 @@ Verder heb ik de vraag ook beantwoord"
|
||||
**Context**: OPERATIONS - Deployment Setup; commit and push for pipeline verification
|
||||
|
||||
---
|
||||
|
||||
## Deployment Setup - Pull Request
|
||||
|
||||
**Timestamp**: 2026-10-18T22:22:48Z
|
||||
|
||||
**User Input**: "okee. kan jij een PR aanmaken? Dan kijk ik wat de PR doet met de workflow. EVentueel mergens we de changes en PR zonder de feature branch te verwijderen zodat wer daarna door kunnen op deze branch met het aan de praat krijgen, maar dan staat de workflow in ieder geval al op master"
|
||||
|
||||
**AI Response**: "Created Gitea PR #3 (feature/frontend-shell -> master) via the API using the stored Git Credential Manager login; body without 4-byte emoji (Gitea DB limitation, attribution line without the robot emoji); body asks to keep the branch on merge. PR mergeable. Workflow run started on the pull_request event (job 'check' running at e643660)."
|
||||
|
||||
**Context**: OPERATIONS - Deployment Setup; pipeline verification via PR #3
|
||||
|
||||
---
|
||||
|
||||
## Deployment Setup - Monitoring PR Run and Test 500
|
||||
|
||||
**Timestamp**: 2026-10-18T22:25:18Z
|
||||
|
||||
**User Input**: "Kan jij de workflow in de gaten houden? Dan kan je zelf kijken wat er mis gaat eventueel. Ik zie wel op test.andreaslop.nl dat ik een 500 error krijg. Klopt dat? De map is namelijk nog leeg"
|
||||
|
||||
**AI Response**: "Checked https://test.andreaslop.nl: 500 from nginx 1.24 with our CSP and X-Robots-Tag headers, so proxy, certbot, Host header and test block work. Cause: empty folder makes try_files fall back to /index.html, which loops (internal redirection cycle -> 500). Changed generator to 'try_files $uri $uri/ /index.html =404' (404 instead of loop), test updated, config regenerated; not pushed yet to avoid cancelling the running PR run. Started a background watcher (Gitea API, 30 s interval, logs status changes and failed job logs) on run 526 for e643660."
|
||||
|
||||
**Context**: OPERATIONS - Deployment Setup; watching PR #3 run
|
||||
|
||||
---
|
||||
|
||||
## Deployment Setup - First CI Run Result
|
||||
|
||||
**Timestamp**: 2026-10-18T22:33:41Z
|
||||
|
||||
**User Input**: "Top. Heb het config bestand aangepast en die heeft nu inderdaad een 404. Ik zie dat de workflow faalt bij de tests"
|
||||
|
||||
**AI Response**: "Owner applied try_files =404 on the hosting Pi (empty folder now 404). Watcher bug: Windows console could not print a check mark from the log and looped instead of exiting; stopped it, fetched job 4574 log via API. Run 526: lint and format passed (line endings fixed by .gitattributes); 92/93 tests passed; '/ rendert binnen de shell' timed out at 5 s (7.0 s on the arm64 Pi; first render per file is slow, e.g. Footer 3.6 s). Set vitest testTimeout 20 s with rationale; silenced the router's expected warning in the crash test. Local: lint, format, 93 tests, tsc pass. Watcher fixed (UTF-8 stdout, logs to file, always exits). Committing and pushing to re-run PR #3."
|
||||
|
||||
**Context**: OPERATIONS - Deployment Setup; fixing CI
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user