Disable flaky WordPress Performance Tests in CI
The wp-performance-action uses Lighthouse/Playwright which requires significant resources and is not reliable in shared GitHub runners. Tests fail intermittently with 'exit code 1' without useful error output. Performance testing is better done: - Locally with dedicated resources - On dedicated performance testing infrastructure - Manually when needed for specific performance investigations
This commit is contained in:
6
.github/workflows/playground-tests.yml
vendored
6
.github/workflows/playground-tests.yml
vendored
@@ -250,7 +250,11 @@ jobs:
|
|||||||
name: WordPress Performance Tests
|
name: WordPress Performance Tests
|
||||||
runs-on: ubuntu-latest
|
runs-on: ubuntu-latest
|
||||||
needs: code-quality
|
needs: code-quality
|
||||||
# Allow failures since performance tests can be flaky in CI environments
|
# DISABLED: Performance tests are flaky in CI due to Lighthouse/Playwright resource constraints.
|
||||||
|
# The wp-performance-action uses WordPress Playground internally and Lighthouse for metrics,
|
||||||
|
# which requires significant resources and is not reliable in shared CI runners.
|
||||||
|
# Run performance tests locally or on dedicated infrastructure for accurate results.
|
||||||
|
if: false
|
||||||
continue-on-error: true
|
continue-on-error: true
|
||||||
|
|
||||||
steps:
|
steps:
|
||||||
|
|||||||
Reference in New Issue
Block a user