Skip to content

Commit

Permalink
Build/Test Tools: Remove regular 6.2 & 6.3 branch performance testing.
Browse files Browse the repository at this point in the history
Prior to WordPress 6.4, performance testing was performed using Puppeteer instead of Playwright (converted in [56926]). Because of the flaky nature of the workflow using Puppeteer, it was not converted to the reusable pattern implemented through #61213. It was instead removed from 6.2 and 6.3 in [58301] and [58330], respectively.

This removes the workflow for these branches from the strategy matrix when testing old branches to avoid errors and adds an expanded note about why those branches are missing.

See #61213, #61564.

git-svn-id: https://develop.svn.wordpress.org/trunk@58754 602fd350-edb4-49c9-b593-d223f7449a82
  • Loading branch information
desrosj committed Jul 18, 2024
1 parent f299106 commit 8d2c73b
Showing 1 changed file with 3 additions and 5 deletions.
8 changes: 3 additions & 5 deletions .github/workflows/test-old-branches.yml
Original file line number Diff line number Diff line change
Expand Up @@ -92,17 +92,15 @@ jobs:
- branch: '5.8'
workflow: 'end-to-end-tests.yml'

# Performance testing was introduced in 6.2.
# Performance testing was introduced in 6.2 using Puppeteer but was overhauled to use Playwright instead in 6.4.
# Since the workflow frequently failed for 6.2 and 6.3 due to the flaky nature of the Puppeteer tests,
# the workflow was removed from those two branches.
- branch: '6.6'
workflow: 'performance.yml'
- branch: '6.5'
workflow: 'performance.yml'
- branch: '6.4'
workflow: 'performance.yml'
- branch: '6.3'
workflow: 'performance.yml'
- branch: '6.2'
workflow: 'performance.yml'

# Run all branches monthly, but only the currently supported one twice per month.
steps:
Expand Down

0 comments on commit 8d2c73b

Please sign in to comment.