Skip to content

Bump the react-native group with 1 update #163

Bump the react-native group with 1 update

Bump the react-native group with 1 update #163

Triggered via pull request March 13, 2024 20:51
Status Failure
Total duration 41m 23s
Artifacts 1

end2end-test.yml

on: pull_request
Matrix: e2e-playwright
Report to GitHub
9s
Report to GitHub
Fit to window
Zoom out
Zoom in

Annotations

16 errors, 9 warnings, and 8 notices
[chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › value is correctly hydrated for different values: test/e2e/specs/interactivity/directive-bind.spec.ts#L218
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
[chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › value is correctly hydrated for different values: test/e2e/specs/interactivity/directive-bind.spec.ts#L218
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
[chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › value is correctly hydrated for different values: test/e2e/specs/interactivity/directive-bind.spec.ts#L218
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
[chromium] › interactivity/directive-class.spec.ts:21:6 › data-wp-class › remove class if callback returns falsy value: test/e2e/specs/interactivity/directive-class.spec.ts#L29
2) [chromium] › interactivity/directive-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/directive-class.spec.ts:29:22
[chromium] › interactivity/directive-class.spec.ts:21:6 › data-wp-class › remove class if callback returns falsy value: test/e2e/specs/interactivity/directive-class.spec.ts#L29
2) [chromium] › interactivity/directive-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/directive-class.spec.ts:29:22
[chromium] › interactivity/directive-class.spec.ts:21:6 › data-wp-class › remove class if callback returns falsy value: test/e2e/specs/interactivity/directive-class.spec.ts#L29
2) [chromium] › interactivity/directive-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/directive-class.spec.ts:29:22
[chromium] › interactivity/directive-class.spec.ts:71:6 › data-wp-class › can toggle class in the middle: test/e2e/specs/interactivity/directive-class.spec.ts#L73
3) [chromium] › interactivity/directive-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/directive-class.spec.ts:73:22
[chromium] › interactivity/directive-class.spec.ts:71:6 › data-wp-class › can toggle class in the middle: test/e2e/specs/interactivity/directive-class.spec.ts#L73
3) [chromium] › interactivity/directive-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/directive-class.spec.ts:73:22
[chromium] › interactivity/directive-class.spec.ts:71:6 › data-wp-class › can toggle class in the middle: test/e2e/specs/interactivity/directive-class.spec.ts#L73
3) [chromium] › interactivity/directive-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/directive-class.spec.ts:73:22
[chromium] › interactivity/directive-style.spec.ts:21:6 › data-wp-style › dont change style if callback returns same value on hydration: test/e2e/specs/interactivity/directive-style.spec.ts#L27
4) [chromium] › interactivity/directive-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/directive-style.spec.ts:27:22
[chromium] › interactivity/router-regions.spec.ts:28:6 › Router regions › should be the only part hydrated: test/e2e/specs/interactivity/router-regions.spec.ts#L36
1) [chromium] › interactivity/router-regions.spec.ts:28:6 › Router regions › should be the only part hydrated Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('no-region-text-1') Expected string: "not hydrated" Received string: "" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('no-region-text-1') - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" 34 | await expect( region1Text ).toHaveText( 'hydrated' ); 35 | await expect( region2Text ).toHaveText( 'hydrated' ); > 36 | await expect( noRegionText1 ).toHaveText( 'not hydrated' ); | ^ 37 | await expect( noRegionText2 ).toHaveText( 'not hydrated' ); 38 | } ); 39 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-regions.spec.ts:36:33
[chromium] › interactivity/router-regions.spec.ts:28:6 › Router regions › should be the only part hydrated: test/e2e/specs/interactivity/router-regions.spec.ts#L36
1) [chromium] › interactivity/router-regions.spec.ts:28:6 › Router regions › should be the only part hydrated Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('no-region-text-1') Expected string: "not hydrated" Received string: "" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('no-region-text-1') - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" 34 | await expect( region1Text ).toHaveText( 'hydrated' ); 35 | await expect( region2Text ).toHaveText( 'hydrated' ); > 36 | await expect( noRegionText1 ).toHaveText( 'not hydrated' ); | ^ 37 | await expect( noRegionText2 ).toHaveText( 'not hydrated' ); 38 | } ); 39 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-regions.spec.ts:36:33
[chromium] › interactivity/router-regions.spec.ts:28:6 › Router regions › should be the only part hydrated: test/e2e/specs/interactivity/router-regions.spec.ts#L36
1) [chromium] › interactivity/router-regions.spec.ts:28:6 › Router regions › should be the only part hydrated Retry #2 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected) Locator: getByTestId('no-region-text-1') Expected string: "not hydrated" Received string: "" Call log: - expect.toHaveText with timeout 5000ms - waiting for getByTestId('no-region-text-1') - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" - locator resolved to <p data-testid="no-region-text-1" data-wp-text="sta…></p> - unexpected value "" 34 | await expect( region1Text ).toHaveText( 'hydrated' ); 35 | await expect( region2Text ).toHaveText( 'hydrated' ); > 36 | await expect( noRegionText1 ).toHaveText( 'not hydrated' ); | ^ 37 | await expect( noRegionText2 ).toHaveText( 'not hydrated' ); 38 | } ); 39 | at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-regions.spec.ts:36:33
Playwright - 7
Process completed with exit code 1.
Playwright - 7
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
Report to GitHub
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
🎭 Playwright Run Summary
1 skipped 177 passed (8.5m)
🎭 Playwright Run Summary
11 skipped 175 passed (8.4m)
🎭 Playwright Run Summary
3 skipped 144 passed (8.1m)
🎭 Playwright Run Summary
183 passed (8.2m)
🎭 Playwright Run Summary
1 skipped 179 passed (8.6m)
🎭 Playwright Run Summary
8 failed [chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › value is correctly hydrated for different values [chromium] › interactivity/directive-class.spec.ts:21:6 › data-wp-class › remove class if callback returns falsy value [chromium] › interactivity/directive-class.spec.ts:71:6 › data-wp-class › can toggle class in the middle [chromium] › interactivity/directive-style.spec.ts:21:6 › data-wp-style › dont change style if callback returns same value on hydration [chromium] › interactivity/directive-style.spec.ts:33:6 › data-wp-style › remove style if callback returns falsy value on hydration [chromium] › interactivity/directive-style.spec.ts:42:6 › data-wp-style › change style if callback returns a new value on hydration [chromium] › interactivity/directive-style.spec.ts:89:6 › data-wp-style › can toggle style in the middle [chromium] › interactivity/directive-style.spec.ts:112:6 › data-wp-style › can use context values 2 skipped 173 passed (8.0m)
🎭 Playwright Run Summary
1 skipped 187 passed (9.2m)
🎭 Playwright Run Summary
1 failed [chromium] › interactivity/router-regions.spec.ts:28:6 › Router regions › should be the only part hydrated 218 passed (13.1m)
Puppeteer
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/.
Playwright - 4
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/.
Playwright - 1
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/.
Playwright - 8
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/.
Playwright - 5
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/.
Playwright - 3
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/.
Playwright - 6
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/.
Playwright - 2
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/.
Playwright - 7
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/.

Artifacts

Produced during runtime
Name Size
failures-artifacts Expired
8.55 MB