From a0b15f354a57a20319aeac636ffdb47d4cc04176 Mon Sep 17 00:00:00 2001 From: Joe McGill Date: Wed, 26 Jul 2023 19:11:44 +0000 Subject: [PATCH] Build/Test Tools: Run performance tests using production env vars. This sets the following environment variables when running automated performance tests to avoid side effects that can skew performance data when the default development environment variables are used: * `SAVEQUERIES`: `false` * `SCRIPT_DEBUG`: `false` * `WP_DEBUG`: `false` * `WP_DEVELOPMENT_MODE`: `''` Props rajinsharwar, desrosj, mukesh27, joemcgill. Fixes #58825. git-svn-id: https://develop.svn.wordpress.org/trunk@56313 602fd350-edb4-49c9-b593-d223f7449a82 --- .github/workflows/performance.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/.github/workflows/performance.yml b/.github/workflows/performance.yml index 408f7ba9f5..7b6b513b37 100644 --- a/.github/workflows/performance.yml +++ b/.github/workflows/performance.yml @@ -30,6 +30,12 @@ concurrency: permissions: {} env: + # Performance testing should be performed in an environment reflecting a standard production environment. + WP_DEBUG: false + SCRIPT_DEBUG: false + SAVEQUERIES : false + WP_DEVELOPMENT_MODE: '' + # This workflow takes two sets of measurements — one for the current commit, # and another against a consistent version that is used as a baseline measurement. # This is done to isolate variance in measurements caused by the GitHub runners