From 340628877cfd14cf86c009bfb3fa9c52eb7f9294 Mon Sep 17 00:00:00 2001
From: marcusquinn <6428977+marcusquinn@users.noreply.github.com>
Date: Mon, 24 Nov 2025 23:49:14 +0000
Subject: [PATCH] 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
---
 .github/workflows/playground-tests.yml | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/playground-tests.yml b/.github/workflows/playground-tests.yml
index 2b71b9c..9377910 100644
--- a/.github/workflows/playground-tests.yml
+++ b/.github/workflows/playground-tests.yml
@@ -250,7 +250,11 @@ jobs:
     name: WordPress Performance Tests
     runs-on: ubuntu-latest
     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
 
     steps: