The artifact name is not valid: test-output-Jetpack Boost - Concatenate JS/CSS. Contains the following character: Forward slash / Invalid characters include: Double quote ", Colon :, Less than <, Greater than >, Vertical bar |, Asterisk *, Question mark ?, Carriage return \r, Line feed \n, Backslash \, Forward slash / These characters are not allowed in the artifact name due to limitations with certain file systems such as NTFS. To maintain file system agnostic behavior, these characters are intentionally not allowed to prevent potential problems with downloads on different file systems.

1) specs/modules/speed-score.test.js:33:2 › Speed Score feature › The Speed Scores should be able to refresh Error: Score should be displayed expect(received).toBeTruthy() Received: null 37 | expect( await jetpackBoostPage.isScoreLoading(), 'Score should be loading' ).toBeTruthy(); 38 | await jetpackBoostPage.waitForScoreLoadingToFinish(); > 39 | expect( await jetpackBoostPage.isScoreVisible(), 'Score should be displayed' ).toBeTruthy(); | ^ 40 | } ); 41 | 42 | test( 'Should be able to click info icon next to overall score and see the detailed overall score description popin', async () => { at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/modules/speed-score.test.js:39:82

1) specs/critical-css/critical-css.test.js:70:2 › Critical CSS module › Critical CSS should be available on the frontend when the module is active TimeoutError: locator.innerText: Timeout 20000ms exceeded. Call log: - waiting for locator('#jetpack-boost-critical-css') 70 | test( 'Critical CSS should be available on the frontend when the module is active', async () => { 71 | await PostFrontendPage.visit( page ); > 72 | const criticalCss = await page.locator( '#jetpack-boost-critical-css' ).innerText(); | ^ 73 | expect( criticalCss.length, 'Critical CSS should be displayed' ).toBeGreaterThan( 100 ); 74 | } ); 75 | at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:72:75

1) specs/critical-css/critical-css.test.js:70:2 › Critical CSS module › Critical CSS should be available on the frontend when the module is active Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.innerText: Timeout 20000ms exceeded. Call log: - waiting for locator('#jetpack-boost-critical-css') 70 | test( 'Critical CSS should be available on the frontend when the module is active', async () => { 71 | await PostFrontendPage.visit( page ); > 72 | const criticalCss = await page.locator( '#jetpack-boost-critical-css' ).innerText(); | ^ 73 | expect( criticalCss.length, 'Critical CSS should be displayed' ).toBeGreaterThan( 100 ); 74 | } ); 75 | at /home/runner/work/jetpack/jetpack/projects/plugins/boost/tests/e2e/specs/critical-css/critical-css.test.js:72:75

Process completed with exit code 1.

2 passed (42.9s)

4 passed (1.1m)

5 passed (1.2m)

5 passed (1.6m)

1 flaky specs/modules/speed-score.test.js:33:2 › Speed Score feature › The Speed Scores should be able to refresh 12 passed (2.2m)

1 failed specs/critical-css/critical-css.test.js:70:2 › Critical CSS module › Critical CSS should be available on the frontend when the module is active 7 passed (2.9m)