1) [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:378:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@Firefox, @WebKit) › submenu click on the arrow interactions Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('link', { name: 'Submenu Link' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('link', { name: 'Submenu Link' }) 424 | // Move the mouse so the hover on the button doesn't keep the menu open 425 | await page.mouse.move( 400, 400 ); > 426 | await expect( firstLevelElement ).toBeVisible(); | ^ 427 | await expect( secondLevelElement ).toBeHidden(); 428 | 429 | // Close menu via click on the body at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:426:38

1) [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:378:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@Firefox, @WebKit) › submenu click on the arrow interactions Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('link', { name: 'Submenu Link' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('link', { name: 'Submenu Link' }) 424 | // Move the mouse so the hover on the button doesn't keep the menu open 425 | await page.mouse.move( 400, 400 ); > 426 | await expect( firstLevelElement ).toBeVisible(); | ^ 427 | await expect( secondLevelElement ).toBeHidden(); 428 | 429 | // Close menu via click on the body at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:426:38

1) [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:378:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@Firefox, @WebKit) › submenu click on the arrow interactions Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('link', { name: 'Submenu Link' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('link', { name: 'Submenu Link' }) 424 | // Move the mouse so the hover on the button doesn't keep the menu open 425 | await page.mouse.move( 400, 400 ); > 426 | await expect( firstLevelElement ).toBeVisible(); | ^ 427 | await expect( secondLevelElement ).toBeHidden(); 428 | 429 | // Close menu via click on the body at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:426:38

2) [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:470:3 › Navigation block - Frontend interactivity › Page list block (@Firefox, @WebKit) › page-list submenu user interactions Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('link', { name: 'Subpage' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('link', { name: 'Subpage' }) 483 | // page-list submenu opens on click 484 | await submenuButton.click(); > 485 | await expect( innerElement ).toBeVisible(); | ^ 486 | 487 | // page-list submenu closes on click outside 488 | await page.click( 'body' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:485:33

2) [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:470:3 › Navigation block - Frontend interactivity › Page list block (@Firefox, @WebKit) › page-list submenu user interactions Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('link', { name: 'Subpage' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('link', { name: 'Subpage' }) 483 | // page-list submenu opens on click 484 | await submenuButton.click(); > 485 | await expect( innerElement ).toBeVisible(); | ^ 486 | 487 | // page-list submenu closes on click outside 488 | await page.click( 'body' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:485:33

2) [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:470:3 › Navigation block - Frontend interactivity › Page list block (@Firefox, @WebKit) › page-list submenu user interactions Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeVisible() Locator: getByRole('link', { name: 'Subpage' }) Expected: visible Received: hidden Call log: - expect.toBeVisible with timeout 5000ms - waiting for getByRole('link', { name: 'Subpage' }) 483 | // page-list submenu opens on click 484 | await submenuButton.click(); > 485 | await expect( innerElement ).toBeVisible(); | ^ 486 | 487 | // page-list submenu closes on click outside 488 | await page.click( 'body' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:485:33

Process completed with exit code 1.

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

1) [chromium] › interactivity/directive-context.spec.ts:55:6 › data-wp-context › changes in inherited properties are reflected (child) Error: expect(received).toBe(expected) // Object.is equality Expected: "modifiedFromChild" Received: "parent" 63 | ); 64 | > 65 | expect( childContext.prop1 ).toBe( 'modifiedFromChild' ); | ^ 66 | expect( childContext.obj.prop4 ).toBe( 'modifiedFromChild' ); 67 | 68 | const parentContext = await parseContent( at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:65:32

1) [chromium] › interactivity/directive-context.spec.ts:55:6 › data-wp-context › changes in inherited properties are reflected (child) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: "modifiedFromChild" Received: "parent" 63 | ); 64 | > 65 | expect( childContext.prop1 ).toBe( 'modifiedFromChild' ); | ^ 66 | expect( childContext.obj.prop4 ).toBe( 'modifiedFromChild' ); 67 | 68 | const parentContext = await parseContent( at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:65:32

1) [chromium] › interactivity/directive-context.spec.ts:55:6 › data-wp-context › changes in inherited properties are reflected (child) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: "modifiedFromChild" Received: "parent" 63 | ); 64 | > 65 | expect( childContext.prop1 ).toBe( 'modifiedFromChild' ); | ^ 66 | expect( childContext.obj.prop4 ).toBe( 'modifiedFromChild' ); 67 | 68 | const parentContext = await parseContent( at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:65:32

2) [chromium] › interactivity/directive-context.spec.ts:76:6 › data-wp-context › changes in inherited properties are reflected (parent) Error: expect(received).toBe(expected) // Object.is equality Expected: "modifiedFromParent" Received: "parent" 84 | ); 85 | > 86 | expect( childContext.prop1 ).toBe( 'modifiedFromParent' ); | ^ 87 | expect( childContext.obj.prop4 ).toBe( 'modifiedFromParent' ); 88 | 89 | const parentContext = await parseContent( at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:86:32

2) [chromium] › interactivity/directive-context.spec.ts:76:6 › data-wp-context › changes in inherited properties are reflected (parent) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: "modifiedFromParent" Received: "parent" 84 | ); 85 | > 86 | expect( childContext.prop1 ).toBe( 'modifiedFromParent' ); | ^ 87 | expect( childContext.obj.prop4 ).toBe( 'modifiedFromParent' ); 88 | 89 | const parentContext = await parseContent( at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:86:32

2) [chromium] › interactivity/directive-context.spec.ts:76:6 › data-wp-context › changes in inherited properties are reflected (parent) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: "modifiedFromParent" Received: "parent" 84 | ); 85 | > 86 | expect( childContext.prop1 ).toBe( 'modifiedFromParent' ); | ^ 87 | expect( childContext.obj.prop4 ).toBe( 'modifiedFromParent' ); 88 | 89 | const parentContext = await parseContent( at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:86:32

3) [chromium] › interactivity/directive-context.spec.ts:97:6 › data-wp-context › changes in shadowed properties do not leak (child) Error: expect(received).toBe(expected) // Object.is equality Expected: "modifiedFromChild" Received: "child" 105 | ); 106 | > 107 | expect( childContext.prop2 ).toBe( 'modifiedFromChild' ); | ^ 108 | expect( childContext.obj.prop5 ).toBe( 'modifiedFromChild' ); 109 | 110 | const parentContext = await parseContent( at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:107:32

3) [chromium] › interactivity/directive-context.spec.ts:97:6 › data-wp-context › changes in shadowed properties do not leak (child) Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: "modifiedFromChild" Received: "child" 105 | ); 106 | > 107 | expect( childContext.prop2 ).toBe( 'modifiedFromChild' ); | ^ 108 | expect( childContext.obj.prop5 ).toBe( 'modifiedFromChild' ); 109 | 110 | const parentContext = await parseContent( at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:107:32

3) [chromium] › interactivity/directive-context.spec.ts:97:6 › data-wp-context › changes in shadowed properties do not leak (child) Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toBe(expected) // Object.is equality Expected: "modifiedFromChild" Received: "child" 105 | ); 106 | > 107 | expect( childContext.prop2 ).toBe( 'modifiedFromChild' ); | ^ 108 | expect( childContext.obj.prop5 ).toBe( 'modifiedFromChild' ); 109 | 110 | const parentContext = await parseContent( at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:107:32

4) [chromium] › interactivity/directive-context.spec.ts:118:6 › data-wp-context › changes in shadowed properties do not leak (parent) Error: expect(received).toBe(expected) // Object.is equality Expected: "modifiedFromParent" Received: "parent" 133 | ); 134 | > 135 | expect( parentContext.prop2 ).toBe( 'modifiedFromParent' ); | ^ 136 | expect( parentContext.obj.prop5 ).toBe( 'modifiedFromParent' ); 137 | } ); 138 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-context.spec.ts:135:33

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

1) [chromium] › editor/blocks/navigation-colors.spec.js:57:2 › Navigation colors › All navigation links should default to the body color and submenus and mobile overlay should default to a white background with black text Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:75:3

1) [chromium] › editor/blocks/navigation-colors.spec.js:57:2 › Navigation colors › All navigation links should default to the body color and submenus and mobile overlay should default to a white background with black text Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:75:3

1) [chromium] › editor/blocks/navigation-colors.spec.js:57:2 › Navigation colors › All navigation links should default to the body color and submenus and mobile overlay should default to a white background with black text Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:75:3

2) [chromium] › editor/blocks/navigation-colors.spec.js:78:2 › Navigation colors › Top level navigation links inherit the text color from the theme/group but do not apply to the submenu or overlay text Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('a').filter({ hasText: 'Custom Link' }) Expected string: "rgb(0, 0, 0)" Received string: "rgb(255, 255, 255)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('a').filter({ hasText: 'Custom Link' }) - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. > 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); | ^ 491 | await expect( submenuLink ).toHaveCSS( 'color', submenuTextColor ); 492 | await expect( pageLink ).toHaveCSS( 'color', submenuTextColor ); 493 | at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:490:30) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:128:3

2) [chromium] › editor/blocks/navigation-colors.spec.js:78:2 › Navigation colors › Top level navigation links inherit the text color from the theme/group but do not apply to the submenu or overlay text Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('a').filter({ hasText: 'Custom Link' }) Expected string: "rgb(0, 0, 0)" Received string: "rgb(255, 255, 255)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('a').filter({ hasText: 'Custom Link' }) - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. > 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); | ^ 491 | await expect( submenuLink ).toHaveCSS( 'color', submenuTextColor ); 492 | await expect( pageLink ).toHaveCSS( 'color', submenuTextColor ); 493 | at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:490:30) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:128:3

2) [chromium] › editor/blocks/navigation-colors.spec.js:78:2 › Navigation colors › Top level navigation links inherit the text color from the theme/group but do not apply to the submenu or overlay text Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('a').filter({ hasText: 'Custom Link' }) Expected string: "rgb(0, 0, 0)" Received string: "rgb(255, 255, 255)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('a').filter({ hasText: 'Custom Link' }) - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" - locator resolved to <a href="https://wordpress.org" class="wp-block-nav…>Custom Link</a> - unexpected value "rgb(255, 255, 255)" 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. > 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); | ^ 491 | await expect( submenuLink ).toHaveCSS( 'color', submenuTextColor ); 492 | await expect( pageLink ).toHaveCSS( 'color', submenuTextColor ); 493 | at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:490:30) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:128:3

3) [chromium] › editor/blocks/navigation-colors.spec.js:131:2 › Navigation colors › Navigation text does not inherit the link color from the theme/group Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:184:3

3) [chromium] › editor/blocks/navigation-colors.spec.js:131:2 › Navigation colors › Navigation text does not inherit the link color from the theme/group Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:184:3

3) [chromium] › editor/blocks/navigation-colors.spec.js:131:2 › Navigation colors › Navigation text does not inherit the link color from the theme/group Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:184:3

4) [chromium] › editor/blocks/navigation-colors.spec.js:187:2 › Navigation colors › The navigation text color should apply to all navigation links including submenu and overlay text Error: Timed out 5000ms waiting for expect(locator).toHaveCSS(expected) Locator: locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) Expected string: "rgb(255, 255, 255)" Received string: "rgba(0, 0, 0, 0)" Call log: - expect.toHaveCSS with timeout 5000ms - waiting for locator('.wp-block-navigation__responsive-container').filter({ hasText: 'Submenu Link' }) - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" - locator resolved to <div id="modal-1" tabindex="-1" data-wp-watch="callba…>…</div> - unexpected value "rgba(0, 0, 0, 0)" 497 | 498 | // The mobile menu background should be the same color as the submenu background. > 499 | await expect( overlayFront ).toHaveCSS( | ^ 500 | 'background-color', 501 | submenuBackgroundColor 502 | ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:499:32) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:226:3

1) [chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation TypeError: resolveLink2 is not a function 90 | await expect( title ).toHaveText( 'Main' ); 91 | > 92 | await Promise.resolve().then( () => resolveLink2() ); | ^ 93 | 94 | await expect( navigations ).toHaveText( '1' ); 95 | await expect( status ).toHaveText( 'busy' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:92:39 at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:92:3

1) [chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TypeError: resolveLink2 is not a function 90 | await expect( title ).toHaveText( 'Main' ); 91 | > 92 | await Promise.resolve().then( () => resolveLink2() ); | ^ 93 | 94 | await expect( navigations ).toHaveText( '1' ); 95 | await expect( status ).toHaveText( 'busy' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:92:39 at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:92:3

1) [chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── TypeError: resolveLink2 is not a function 90 | await expect( title ).toHaveText( 'Main' ); 91 | > 92 | await Promise.resolve().then( () => resolveLink2() ); | ^ 93 | 94 | await expect( navigations ).toHaveText( '1' ); 95 | await expect( status ).toHaveText( 'busy' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:92:39 at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:92:3

2) [chromium] › interactivity/router-navigate.spec.ts:105:6 › Router navigate › should update the URL from the last navigation if only varies in the URL fragment TypeError: resolvers.pop(...) is not a function 134 | await expect( title ).toHaveText( 'Main' ); 135 | > 136 | resolvers.pop()!(); | ^ 137 | 138 | await expect( navigations ).toHaveText( '1' ); 139 | await expect( status ).toHaveText( 'busy' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:136:18

2) [chromium] › interactivity/router-navigate.spec.ts:105:6 › Router navigate › should update the URL from the last navigation if only varies in the URL fragment Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── TypeError: resolvers.pop(...) is not a function 134 | await expect( title ).toHaveText( 'Main' ); 135 | > 136 | resolvers.pop()!(); | ^ 137 | 138 | await expect( navigations ).toHaveText( '1' ); 139 | await expect( status ).toHaveText( 'busy' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:136:18

2) [chromium] › interactivity/router-navigate.spec.ts:105:6 › Router navigate › should update the URL from the last navigation if only varies in the URL fragment Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── TypeError: resolvers.pop(...) is not a function 134 | await expect( title ).toHaveText( 'Main' ); 135 | > 136 | resolvers.pop()!(); | ^ 137 | 138 | await expect( navigations ).toHaveText( '1' ); 139 | await expect( status ).toHaveText( 'busy' ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:136:18

3) [chromium] › interactivity/router-navigate.spec.ts:151:6 › Router navigate › should reload the next page when the timeout ends Error: Timed out 5000ms waiting for expect(locator).toHaveURL(expected) Locator: locator(':root') Expected string: "http://localhost:8889/?p=31&disable_server_directive_processing=true" Received string: "http://localhost:8889/?p=33&disable_server_directive_processing=true" Call log: - expect.toHaveURL with timeout 5000ms - waiting for locator(':root') - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=33&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=33&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=33&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=33&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=33&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=33&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=33&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=33&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=33&disable_server_directive_processing=true" 179 | await page.getByTestId( 'link 1' ).click(); 180 | > 181 | await expect( page ).toHaveURL( link1 ); | ^ 182 | await expect( title ).toHaveText( 'Link 1' ); 183 | 184 | // If timeout is 10000, that means the page has been reloaded. at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:181:24

3) [chromium] › interactivity/router-navigate.spec.ts:151:6 › Router navigate › should reload the next page when the timeout ends Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveURL(expected) Locator: locator(':root') Expected string: "http://localhost:8889/?p=35&disable_server_directive_processing=true" Received string: "http://localhost:8889/?p=37&disable_server_directive_processing=true" Call log: - expect.toHaveURL with timeout 5000ms - waiting for locator(':root') - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=37&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=37&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=37&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=37&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=37&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=37&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=37&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=37&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=37&disable_server_directive_processing=true" 179 | await page.getByTestId( 'link 1' ).click(); 180 | > 181 | await expect( page ).toHaveURL( link1 ); | ^ 182 | await expect( title ).toHaveText( 'Link 1' ); 183 | 184 | // If timeout is 10000, that means the page has been reloaded. at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:181:24

3) [chromium] › interactivity/router-navigate.spec.ts:151:6 › Router navigate › should reload the next page when the timeout ends Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveURL(expected) Locator: locator(':root') Expected string: "http://localhost:8889/?p=39&disable_server_directive_processing=true" Received string: "http://localhost:8889/?p=41&disable_server_directive_processing=true" Call log: - expect.toHaveURL with timeout 5000ms - waiting for locator(':root') - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=41&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=41&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=41&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=41&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=41&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=41&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=41&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=41&disable_server_directive_processing=true" - locator resolved to <html lang="en-US">…</html> - unexpected value "http://localhost:8889/?p=41&disable_server_directive_processing=true" 179 | await page.getByTestId( 'link 1' ).click(); 180 | > 181 | await expect( page ).toHaveURL( link1 ); | ^ 182 | await expect( title ).toHaveText( 'Link 1' ); 183 | 184 | // If timeout is 10000, that means the page has been reloaded. at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:181:24

4) [chromium] › interactivity/router-navigate.spec.ts:214:6 › Router navigate › should overwrite the state with the one serialized in the new page Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('prop1') Expected string: "link 1" Received string: "main" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('prop1') - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" - locator resolved to <div data-testid="prop1" data-wp-text="state.data.pro…>main</div> - unexpected value "main" 228 | // Old values not overwritten should remain the same. 229 | // New properties should appear. > 230 | await expect( prop1 ).toHaveText( 'link 1' ); | ^ 231 | await expect( prop2 ).toHaveText( 'main' ); 232 | await expect( prop3 ).toHaveText( 'link 1' ); 233 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:230:25

Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Unable to download artifact(s): Artifact not found for name: flaky-tests-report Please ensure that your artifact is not expired and the artifact was uploaded using a compatible version of toolkit/upload-artifact. For more information, visit the GitHub Artifacts FAQ: https://github.com/actions/toolkit/blob/main/packages/artifact/docs/faq.md

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c, actions/cache@88522ab9f39a2ea568f7027eddc7d8d8bc9d59c8. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

185 passed (8.6m)

2 failed [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:378:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@Firefox, @WebKit) › submenu click on the arrow interactions [firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:470:3 › Navigation block - Frontend interactivity › Page list block (@Firefox, @WebKit) › page-list submenu user interactions 3 skipped 143 passed (8.7m)

1 skipped 184 passed (9.3m)

11 skipped 180 passed (9.3m)

1 skipped 177 passed (8.9m)

16 failed [chromium] › interactivity/directive-context.spec.ts:55:6 › data-wp-context › changes in inherited properties are reflected (child) [chromium] › interactivity/directive-context.spec.ts:76:6 › data-wp-context › changes in inherited properties are reflected (parent) [chromium] › interactivity/directive-context.spec.ts:97:6 › data-wp-context › changes in shadowed properties do not leak (child) [chromium] › interactivity/directive-context.spec.ts:118:6 › data-wp-context › changes in shadowed properties do not leak (parent) [chromium] › interactivity/directive-context.spec.ts:139:6 › data-wp-context › new inherited properties update child contexts [chromium] › interactivity/directive-context.spec.ts:233:6 › data-wp-context › should replace values on navigation [chromium] › interactivity/directive-context.spec.ts:251:6 › data-wp-context › should update values when navigating back or forward [chromium] › interactivity/directive-context.spec.ts:263:6 › data-wp-context › should inherit values on navigation [chromium] › interactivity/directive-context.spec.ts:284:6 › data-wp-context › should maintain the same context reference on async actions [chromium] › interactivity/directive-context.spec.ts:303:6 › data-wp-context › references to objects are kept [chromium] › interactivity/directive-each.spec.ts:302:6 › data-wp-each › should work on navigation [chromium] › interactivity/directive-key.spec.ts:21:6 › data-wp-key › should keep the elements when adding items to the start of the array [chromium] › interactivity/directive-on.spec.ts:31:6 › data-wp-on › callbacks should receive the dispatched event [chromium] › interactivity/directive-on.spec.ts:39:6 › data-wp-on › callbacks should be able to access the context [chromium] › interactivity/directive-on.spec.ts:47:6 › data-wp-on › should work with custom events [chromium] › interactivity/directive-run.spec.ts:36:6 › data-wp-run › should work with client-side navigation 3 skipped 165 passed (10.1m)

11 failed [chromium] › editor/blocks/navigation-colors.spec.js:57:2 › Navigation colors › All navigation links should default to the body color and submenus and mobile overlay should default to a white background with black text [chromium] › editor/blocks/navigation-colors.spec.js:78:2 › Navigation colors › Top level navigation links inherit the text color from the theme/group but do not apply to the submenu or overlay text [chromium] › editor/blocks/navigation-colors.spec.js:131:2 › Navigation colors › Navigation text does not inherit the link color from the theme/group [chromium] › editor/blocks/navigation-colors.spec.js:187:2 › Navigation colors › The navigation text color should apply to all navigation links including submenu and overlay text [chromium] › editor/blocks/navigation-colors.spec.js:274:2 › Navigation colors › As a user I expect my navigation to use the colors I selected for it [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:47:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:93:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions in Safari (@WebKit) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:169:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:268:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions on Safari (@WebKit) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:378:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@Firefox, @WebKit) › submenu click on the arrow interactions [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:470:3 › Navigation block - Frontend interactivity › Page list block (@Firefox, @WebKit) › page-list submenu user interactions 1 skipped 180 passed (16.4m)