1) [chromium] › editor/various/dropdown-menu.spec.js:11:2 › Dropdown Menu › keyboard navigiation › allows navigation through each item using arrow keys Error: Timed out 5000ms waiting for expect(locator).toBeFocused() Locator: locator('[role="menuitem"], [role="menuitemcheckbox"], [role="menuitemradio"]').first() Expected: focused Received: inactive Call log: - expect.toBeFocused with timeout 5000ms - waiting for locator('[role="menuitem"], [role="menuitemcheckbox"], [role="menuitemradio"]').first() - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" 24 | await test.step( 'allows navigation through each item using arrow keys', async () => { 25 | // Expect the first menu item to be focused. > 26 | await expect( menuItems.first() ).toBeFocused(); | ^ 27 | 28 | // Arrow down to the last item. 29 | await pageUtils.pressKeys( 'ArrowDown', { times: totalItems - 1 } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/dropdown-menu.spec.js:26:38 at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/dropdown-menu.spec.js:24:14

1) [chromium] › editor/various/dropdown-menu.spec.js:11:2 › Dropdown Menu › keyboard navigiation › allows navigation through each item using arrow keys Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeFocused() Locator: locator('[role="menuitem"], [role="menuitemcheckbox"], [role="menuitemradio"]').first() Expected: focused Received: inactive Call log: - expect.toBeFocused with timeout 5000ms - waiting for locator('[role="menuitem"], [role="menuitemcheckbox"], [role="menuitemradio"]').first() - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" 24 | await test.step( 'allows navigation through each item using arrow keys', async () => { 25 | // Expect the first menu item to be focused. > 26 | await expect( menuItems.first() ).toBeFocused(); | ^ 27 | 28 | // Arrow down to the last item. 29 | await pageUtils.pressKeys( 'ArrowDown', { times: totalItems - 1 } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/dropdown-menu.spec.js:26:38 at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/dropdown-menu.spec.js:24:14

1) [chromium] › editor/various/dropdown-menu.spec.js:11:2 › Dropdown Menu › keyboard navigiation › allows navigation through each item using arrow keys Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toBeFocused() Locator: locator('[role="menuitem"], [role="menuitemcheckbox"], [role="menuitemradio"]').first() Expected: focused Received: inactive Call log: - expect.toBeFocused with timeout 5000ms - waiting for locator('[role="menuitem"], [role="menuitemcheckbox"], [role="menuitemradio"]').first() - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" - locator resolved to <a href="#" class="ab-item" role="menuitem" aria-ex…>…</a> - unexpected value "not focused" 24 | await test.step( 'allows navigation through each item using arrow keys', async () => { 25 | // Expect the first menu item to be focused. > 26 | await expect( menuItems.first() ).toBeFocused(); | ^ 27 | 28 | // Arrow down to the last item. 29 | await pageUtils.pressKeys( 'ArrowDown', { times: totalItems - 1 } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/dropdown-menu.spec.js:26:38 at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/various/dropdown-menu.spec.js:24:14

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-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › value is correctly hydrated for different values Error: expect(received).toEqual(expected) // deep equality - Expected - 1 + Received + 1 Array [ "true", - null, + "", ] 216 | name 217 | ); > 218 | expect( [ type, hydratedAttr ] ).toEqual( [ | ^ 219 | type, 220 | attrValue, 221 | ] ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:218:39

1) [chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › value is correctly hydrated for different values Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toEqual(expected) // deep equality - Expected - 1 + Received + 1 Array [ "true", - null, + "", ] 216 | name 217 | ); > 218 | expect( [ type, hydratedAttr ] ).toEqual( [ | ^ 219 | type, 220 | attrValue, 221 | ] ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:218:39

1) [chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › value is correctly hydrated for different values Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: expect(received).toEqual(expected) // deep equality - Expected - 1 + Received + 1 Array [ "true", - null, + "", ] 216 | name 217 | ); > 218 | expect( [ type, hydratedAttr ] ).toEqual( [ | ^ 219 | type, 220 | attrValue, 221 | ] ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:218:39

Process completed with exit code 1.

1) [chromium] › interactivity/directives-class.spec.ts:21:6 › data-wp-class › remove class if callback returns falsy value Error: Timed out 5000ms waiting for expect(locator).toHaveClass(expected) Locator: getByTestId('remove class if callback returns falsy value') Expected string: "foo bar" Received string: " bar foo" Call log: - expect.toHaveClass with timeout 5000ms - waiting for getByTestId('remove class if callback returns falsy value') - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" 27 | await expect( el ).toHaveClass( 'bar' ); 28 | await page.getByTestId( 'toggle falseValue' ).click(); > 29 | await expect( el ).toHaveClass( 'foo bar' ); | ^ 30 | await page.getByTestId( 'toggle falseValue' ).click(); 31 | await expect( el ).toHaveClass( 'bar' ); 32 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-class.spec.ts:29:22

1) [chromium] › interactivity/directives-class.spec.ts:21:6 › data-wp-class › remove class if callback returns falsy value Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveClass(expected) Locator: getByTestId('remove class if callback returns falsy value') Expected string: "foo bar" Received string: " bar foo" Call log: - expect.toHaveClass with timeout 5000ms - waiting for getByTestId('remove class if callback returns falsy value') - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" 27 | await expect( el ).toHaveClass( 'bar' ); 28 | await page.getByTestId( 'toggle falseValue' ).click(); > 29 | await expect( el ).toHaveClass( 'foo bar' ); | ^ 30 | await page.getByTestId( 'toggle falseValue' ).click(); 31 | await expect( el ).toHaveClass( 'bar' ); 32 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-class.spec.ts:29:22

1) [chromium] › interactivity/directives-class.spec.ts:21:6 › data-wp-class › remove class if callback returns falsy value Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveClass(expected) Locator: getByTestId('remove class if callback returns falsy value') Expected string: "foo bar" Received string: " bar foo" Call log: - expect.toHaveClass with timeout 5000ms - waiting for getByTestId('remove class if callback returns falsy value') - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" - locator resolved to <div class=" bar foo" data-wp-class--foo="state.false…></div> - unexpected value " bar foo" 27 | await expect( el ).toHaveClass( 'bar' ); 28 | await page.getByTestId( 'toggle falseValue' ).click(); > 29 | await expect( el ).toHaveClass( 'foo bar' ); | ^ 30 | await page.getByTestId( 'toggle falseValue' ).click(); 31 | await expect( el ).toHaveClass( 'bar' ); 32 | } ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-class.spec.ts:29:22

2) [chromium] › interactivity/directives-class.spec.ts:71:6 › data-wp-class › can toggle class in the middle Error: Timed out 5000ms waiting for expect(locator).toHaveClass(expected) Locator: getByTestId('can toggle class in the middle') Expected string: "foo bar baz" Received string: "foo baz bar" Call log: - expect.toHaveClass with timeout 5000ms - waiting for getByTestId('can toggle class in the middle') - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" 71 | test( 'can toggle class in the middle', async ( { page } ) => { 72 | const el = page.getByTestId( 'can toggle class in the middle' ); > 73 | await expect( el ).toHaveClass( 'foo bar baz' ); | ^ 74 | await page.getByTestId( 'toggle trueValue' ).click(); 75 | await expect( el ).toHaveClass( 'foo baz' ); 76 | await page.getByTestId( 'toggle trueValue' ).click(); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-class.spec.ts:73:22

2) [chromium] › interactivity/directives-class.spec.ts:71:6 › data-wp-class › can toggle class in the middle Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveClass(expected) Locator: getByTestId('can toggle class in the middle') Expected string: "foo bar baz" Received string: "foo baz bar" Call log: - expect.toHaveClass with timeout 5000ms - waiting for getByTestId('can toggle class in the middle') - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" 71 | test( 'can toggle class in the middle', async ( { page } ) => { 72 | const el = page.getByTestId( 'can toggle class in the middle' ); > 73 | await expect( el ).toHaveClass( 'foo bar baz' ); | ^ 74 | await page.getByTestId( 'toggle trueValue' ).click(); 75 | await expect( el ).toHaveClass( 'foo baz' ); 76 | await page.getByTestId( 'toggle trueValue' ).click(); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-class.spec.ts:73:22

2) [chromium] › interactivity/directives-class.spec.ts:71:6 › data-wp-class › can toggle class in the middle Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveClass(expected) Locator: getByTestId('can toggle class in the middle') Expected string: "foo bar baz" Received string: "foo baz bar" Call log: - expect.toHaveClass with timeout 5000ms - waiting for getByTestId('can toggle class in the middle') - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" - locator resolved to <div class="foo baz bar" data-wp-class--bar="state.tr…></div> - unexpected value "foo baz bar" 71 | test( 'can toggle class in the middle', async ( { page } ) => { 72 | const el = page.getByTestId( 'can toggle class in the middle' ); > 73 | await expect( el ).toHaveClass( 'foo bar baz' ); | ^ 74 | await page.getByTestId( 'toggle trueValue' ).click(); 75 | await expect( el ).toHaveClass( 'foo baz' ); 76 | await page.getByTestId( 'toggle trueValue' ).click(); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-class.spec.ts:73:22

3) [chromium] › interactivity/directives-style.spec.ts:21:6 › data-wp-style › dont change style if callback returns same value on hydration Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected) Locator: getByTestId('dont change style if callback returns same value on hydration') Expected string: "color: red; background: green;" Received string: "background: green; color: red;" Call log: - expect.toHaveAttribute with timeout 5000ms - waiting for getByTestId('dont change style if callback returns same value on hydration') - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" 25 | 'dont change style if callback returns same value on hydration' 26 | ); > 27 | await expect( el ).toHaveAttribute( | ^ 28 | 'style', 29 | 'color: red; background: green;' 30 | ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-style.spec.ts:27:22

3) [chromium] › interactivity/directives-style.spec.ts:21:6 › data-wp-style › dont change style if callback returns same value on hydration Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected) Locator: getByTestId('dont change style if callback returns same value on hydration') Expected string: "color: red; background: green;" Received string: "background: green; color: red;" Call log: - expect.toHaveAttribute with timeout 5000ms - waiting for getByTestId('dont change style if callback returns same value on hydration') - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" 25 | 'dont change style if callback returns same value on hydration' 26 | ); > 27 | await expect( el ).toHaveAttribute( | ^ 28 | 'style', 29 | 'color: red; background: green;' 30 | ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-style.spec.ts:27:22

3) [chromium] › interactivity/directives-style.spec.ts:21:6 › data-wp-style › dont change style if callback returns same value on hydration Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected) Locator: getByTestId('dont change style if callback returns same value on hydration') Expected string: "color: red; background: green;" Received string: "background: green; color: red;" Call log: - expect.toHaveAttribute with timeout 5000ms - waiting for getByTestId('dont change style if callback returns same value on hydration') - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" - locator resolved to <div data-wp-style--color="state.color" data-testid="…>Don’t change style if callback returns same value…</div> - unexpected value "background: green; color: red;" 25 | 'dont change style if callback returns same value on hydration' 26 | ); > 27 | await expect( el ).toHaveAttribute( | ^ 28 | 'style', 29 | 'color: red; background: green;' 30 | ); at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-style.spec.ts:27:22

4) [chromium] › interactivity/directives-style.spec.ts:33:6 › data-wp-style › remove style if callback returns falsy value on hydration Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected) Locator: getByTestId('remove style if callback returns falsy value on hydration') Expected string: "background: green;" Received string: "background:green;" Call log: - expect.toHaveAttribute with timeout 5000ms - waiting for getByTestId('remove style if callback returns falsy value on hydration') - locator resolved to <div data-wp-style--color="state.falseValue" data-tes…>Remove style if callback returns falsy value on h…</div> - unexpected value "background:green;" - locator resolved to <div data-wp-style--color="state.falseValue" data-tes…>Remove style if callback returns falsy value on h…</div> - unexpected value "background:green;" - locator resolved to <div data-wp-style--color="state.falseValue" data-tes…>Remove style if callback returns falsy value on h…</div> - unexpected value "background:green;" - locator resolved to <div data-wp-style--color="state.falseValue" data-tes…>Remove style if callback returns falsy value on h…</div> - unexpected value "background:green;" - locator resolved to <div data-wp-style--color="state.falseValue" data-tes…>Remove style if callback returns falsy value on h…</div> - unexpected value "background:green;" - locator resolved to <div data-wp-style--color="state.falseValue" data-tes…>Remove style if callback returns falsy value on h…</div> - unexpected value "background:green;" - locator resolved to <div data-wp-style--color="state.falseValue" data-tes…>Remove style if callback returns falsy value on h…</div> - unexpected value "background:green;" - locator resolved to <div data-wp-style--color="state.falseValue" data-tes…>Remove style if callback returns falsy value on h…</div> - unexpected value "background:green;" - locator resolved to <div data-wp-style--color="state.falseValue" data-tes…>Remove style if callback returns falsy value on h…</div> - unexpected value "background:green;" 37 | 'remove style if callback returns falsy value on hydration' 38 | ); > 39 | await expect( el ).toHaveAttribute( 'style', 'background: green;' ); | ^ 40 | } ); 41 | 42 | test( 'change style if callback returns a new value on hydration', async ( { at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directives-style.spec.ts:39:22

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

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 TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('button', { name: 'Open menu' }) ============================================================ 485 | // Open the frontend overlay so we can test the colors. 486 | await this.pageUtils.setBrowserViewport( { width: 599, height: 700 } ); > 487 | await this.page.getByRole( 'button', { name: 'Open menu' } ).click(); | ^ 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:487:64) 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 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('button', { name: 'Open menu' }) ============================================================ 485 | // Open the frontend overlay so we can test the colors. 486 | await this.pageUtils.setBrowserViewport( { width: 599, height: 700 } ); > 487 | await this.page.getByRole( 'button', { name: 'Open menu' } ).click(); | ^ 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:487:64) 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 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('button', { name: 'Open menu' }) ============================================================ 485 | // Open the frontend overlay so we can test the colors. 486 | await this.pageUtils.setBrowserViewport( { width: 599, height: 700 } ); > 487 | await this.page.getByRole( 'button', { name: 'Open menu' } ).click(); | ^ 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:487:64) 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 TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('button', { name: 'Open menu' }) ============================================================ 485 | // Open the frontend overlay so we can test the colors. 486 | await this.pageUtils.setBrowserViewport( { width: 599, height: 700 } ); > 487 | await this.page.getByRole( 'button', { name: 'Open menu' } ).click(); | ^ 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:487:64) 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 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('button', { name: 'Open menu' }) ============================================================ 485 | // Open the frontend overlay so we can test the colors. 486 | await this.pageUtils.setBrowserViewport( { width: 599, height: 700 } ); > 487 | await this.page.getByRole( 'button', { name: 'Open menu' } ).click(); | ^ 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:487:64) 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 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('button', { name: 'Open menu' }) ============================================================ 485 | // Open the frontend overlay so we can test the colors. 486 | await this.pageUtils.setBrowserViewport( { width: 599, height: 700 } ); > 487 | await this.page.getByRole( 'button', { name: 'Open menu' } ).click(); | ^ 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:487:64) 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 TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('button', { name: 'Open menu' }) ============================================================ 485 | // Open the frontend overlay so we can test the colors. 486 | await this.pageUtils.setBrowserViewport( { width: 599, height: 700 } ); > 487 | await this.page.getByRole( 'button', { name: 'Open menu' } ).click(); | ^ 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:487:64) 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 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('button', { name: 'Open menu' }) ============================================================ 485 | // Open the frontend overlay so we can test the colors. 486 | await this.pageUtils.setBrowserViewport( { width: 599, height: 700 } ); > 487 | await this.page.getByRole( 'button', { name: 'Open menu' } ).click(); | ^ 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:487:64) 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 ─────────────────────────────────────────────────────────────────────────────────────── TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('button', { name: 'Open menu' }) ============================================================ 485 | // Open the frontend overlay so we can test the colors. 486 | await this.pageUtils.setBrowserViewport( { width: 599, height: 700 } ); > 487 | await this.page.getByRole( 'button', { name: 'Open menu' } ).click(); | ^ 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:487:64) 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 TimeoutError: locator.click: Timeout 10000ms exceeded. =========================== logs =========================== waiting for getByRole('button', { name: 'Open menu' }) ============================================================ 485 | // Open the frontend overlay so we can test the colors. 486 | await this.pageUtils.setBrowserViewport( { width: 599, height: 700 } ); > 487 | await this.page.getByRole( 'button', { name: 'Open menu' } ).click(); | ^ 488 | 489 | // All of the mobile menu navigation links should be the same color as the submenuTextColor. 490 | await expect( customLink ).toHaveCSS( 'color', submenuTextColor ); at ColorControl.testFrontendColors (/home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:487:64) at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-colors.spec.js:226:3

Unable to download artifact(s): Artifact not found for name: flaky-tests-report

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/.

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/.

1 skipped 145 passed (6.2m)

149 passed (6.7m)

1 failed [chromium] › editor/various/dropdown-menu.spec.js:11:2 › Dropdown Menu › keyboard navigiation ── 145 passed (7.3m)

11 skipped 152 passed (7.3m)

3 skipped 119 passed (7.1m)

1 failed [chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › value is correctly hydrated for different values 2 skipped 147 passed (9.0m)

9 failed [chromium] › interactivity/directives-class.spec.ts:21:6 › data-wp-class › remove class if callback returns falsy value [chromium] › interactivity/directives-class.spec.ts:71:6 › data-wp-class › can toggle class in the middle [chromium] › interactivity/directives-style.spec.ts:21:6 › data-wp-style › dont change style if callback returns same value on hydration [chromium] › interactivity/directives-style.spec.ts:33:6 › data-wp-style › remove style if callback returns falsy value on hydration [chromium] › interactivity/directives-style.spec.ts:42:6 › data-wp-style › change style if callback returns a new value on hydration [chromium] › interactivity/directives-style.spec.ts:89:6 › data-wp-style › can toggle style in the middle [chromium] › interactivity/directives-style.spec.ts:112:6 › data-wp-style › can use context values [chromium] › interactivity/router-regions.spec.ts:28:6 › Router regions › should be the only part hydrated [webkit] › editor/blocks/navigation-frontend-interactivity.spec.js:91:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions in Safari (@WebKit) 157 passed (9.8m)