Makes Lighthouse performance report-only in CI
Lighthouse slows the CPU 4x relative to the measuring machine, so the Raspberry Pi runner scores performance 30-40 points lower than a PC for the same build. In CI the performance assertions now only warn; accessibility, best practices and SEO still block, and performance still blocks in `pnpm check` on a PC. Mobile and desktop reports go to separate folders and are attached to every run as an artifact. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -678,3 +678,27 @@ Verder heb ik de vraag ook beantwoord"
|
||||
**Context**: OPERATIONS - Deployment Setup; fixing CI
|
||||
|
||||
---
|
||||
|
||||
## Deployment Setup - CI Run 529 and Lighthouse Question
|
||||
|
||||
**Timestamp**: 2026-10-18T23:13:48Z
|
||||
|
||||
**User Input**: "Wat is de melding \"GitHub token not set\" in de lighthouse job?"
|
||||
|
||||
**AI Response**: "Explained: lhci healthcheck warning (not a failure) because Gitea sets GITHUB_* compat env vars and an upload target is configured; lhci can only post GitHub status checks. Left as is. Run 529: --disable-dev-shm-usage fixed the crash; Lighthouse ran on all 7 pages; accessibility, best practices and SEO passed; performance failed everywhere (0.49-0.66 vs 0.82-0.95 locally). Cause: Lighthouse simulates 4x CPU slowdown relative to the host; local benchmarkIndex 4192, the Pi is far slower, so perf is not representative. Created operations/plans/lighthouse-ci-questions.md (A: perf report-only in CI, blocking locally; B: calibrate CPU multiplier; C: no Lighthouse in CI)."
|
||||
|
||||
**Context**: OPERATIONS - Deployment Setup; awaiting decision
|
||||
|
||||
---
|
||||
|
||||
## Deployment Setup - Lighthouse Performance Report-only in CI
|
||||
|
||||
**Timestamp**: 2026-10-18T23:22:33Z
|
||||
|
||||
**User Input**: "Ja mee eens. Optie A. Kan jij die optie in het bestand bij het antwoord toevoegen en het dan uitvoeren? Dan kan je daarna meteen comitten en pushen. Ik heb de master branch protected gemaakt en de workflow check onderdeel als vereiste ingesteld om te slagen. Zodra je gepusht hebt laat het even weten dat zet ik auto merge aan zodat ik zsm de workflow met deploy kan laten runnen ."
|
||||
|
||||
**AI Response**: "Filled answer A. lighthouserc.cjs: performance assertion level from LIGHTHOUSE_PERFORMANCE (warn in CI, error otherwise), exported for the desktop config; reports to lighthouse-reports/mobile and /desktop (ignored by git, prettier, eslint). Workflow sets LIGHTHOUSE_PERFORMANCE=warn and uploads lighthouse-reports as artifact (if: always()). Verified: config levels per env; full pnpm lighthouse with warn exits 0 with 7+7 HTML reports. Docs updated: NFR-P-01, deployment-plan D6, performance-test-instructions. Committing and pushing; owner will enable auto-merge on PR #3 (master protected, check required)."
|
||||
|
||||
**Context**: OPERATIONS - Deployment Setup; fixing CI
|
||||
|
||||
---
|
||||
|
||||
Reference in New Issue
Block a user