Interactivity API: Fix null and number strings as namespaces runtime error. #105041
cbravobernalAnnotations
48 errors and 8 notices
|
[firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:378:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@firefox:
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L426
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
|
|
[firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:378:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@firefox:
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L426
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
|
|
[firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:378:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@firefox:
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L426
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
|
|
[firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:470:3 › Navigation block - Frontend interactivity › Page list block (@firefox:
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L485
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
|
|
[firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:470:3 › Navigation block - Frontend interactivity › Page list block (@firefox:
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L485
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
|
|
[firefox] › editor/blocks/navigation-frontend-interactivity.spec.js:470:3 › Navigation block - Frontend interactivity › Page list block (@firefox:
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L485
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
|
|
Playwright - 8
Process completed with exit code 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:
test/e2e/specs/editor/blocks/navigation-colors.spec.js#L499
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
|
|
[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:
test/e2e/specs/editor/blocks/navigation-colors.spec.js#L499
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
|
|
[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:
test/e2e/specs/editor/blocks/navigation-colors.spec.js#L499
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
|
|
[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:
test/e2e/specs/editor/blocks/navigation-colors.spec.js#L490
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
|
|
[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:
test/e2e/specs/editor/blocks/navigation-colors.spec.js#L490
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
|
|
[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:
test/e2e/specs/editor/blocks/navigation-colors.spec.js#L490
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
|
|
[chromium] › editor/blocks/navigation-colors.spec.js:131:2 › Navigation colors › Navigation text does not inherit the link color from the theme/group:
test/e2e/specs/editor/blocks/navigation-colors.spec.js#L499
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
|
|
[chromium] › editor/blocks/navigation-colors.spec.js:131:2 › Navigation colors › Navigation text does not inherit the link color from the theme/group:
test/e2e/specs/editor/blocks/navigation-colors.spec.js#L499
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
|
|
[chromium] › editor/blocks/navigation-colors.spec.js:131:2 › Navigation colors › Navigation text does not inherit the link color from the theme/group:
test/e2e/specs/editor/blocks/navigation-colors.spec.js#L499
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
|
|
[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:
test/e2e/specs/editor/blocks/navigation-colors.spec.js#L499
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
|
|
[chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:47:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions:
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L63
1) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:47:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByRole('link', { name: 'Item 1' })
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByRole('link', { name: 'Item 1' })
61 | await expect( overlayMenuFirstElement ).toBeHidden();
62 | await openMenuButton.click();
> 63 | await expect( overlayMenuFirstElement ).toBeVisible();
| ^
64 |
65 | // Test: overlay menu focuses on first element after opening
66 | await expect( overlayMenuFirstElement ).toBeFocused();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:63:44
|
|
[chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:47:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions:
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L63
1) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:47:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByRole('link', { name: 'Item 1' })
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByRole('link', { name: 'Item 1' })
61 | await expect( overlayMenuFirstElement ).toBeHidden();
62 | await openMenuButton.click();
> 63 | await expect( overlayMenuFirstElement ).toBeVisible();
| ^
64 |
65 | // Test: overlay menu focuses on first element after opening
66 | await expect( overlayMenuFirstElement ).toBeFocused();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:63:44
|
|
[chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:47:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions:
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L63
1) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:47:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByRole('link', { name: 'Item 1' })
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByRole('link', { name: 'Item 1' })
61 | await expect( overlayMenuFirstElement ).toBeHidden();
62 | await openMenuButton.click();
> 63 | await expect( overlayMenuFirstElement ).toBeVisible();
| ^
64 |
65 | // Test: overlay menu focuses on first element after opening
66 | await expect( overlayMenuFirstElement ).toBeFocused();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:63:44
|
|
[chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:93:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions in Safari (@webkit):
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L112
2) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:93:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions in Safari (@WebKit)
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByRole('link', { name: 'Item 1' })
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByRole('link', { name: 'Item 1' })
110 | await expect( overlayMenuFirstElement ).toBeHidden();
111 | await openMenuButton.click();
> 112 | await expect( overlayMenuFirstElement ).toBeVisible();
| ^
113 |
114 | // Test: overlay menu focuses on first element after opening
115 | await expect( overlayMenuFirstElement ).toBeFocused();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:112:44
|
|
[chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:93:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions in Safari (@webkit):
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L112
2) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:93:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions in Safari (@WebKit)
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByRole('link', { name: 'Item 1' })
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByRole('link', { name: 'Item 1' })
110 | await expect( overlayMenuFirstElement ).toBeHidden();
111 | await openMenuButton.click();
> 112 | await expect( overlayMenuFirstElement ).toBeVisible();
| ^
113 |
114 | // Test: overlay menu focuses on first element after opening
115 | await expect( overlayMenuFirstElement ).toBeFocused();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:112:44
|
|
[chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:93:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions in Safari (@webkit):
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L112
2) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:93:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions in Safari (@WebKit)
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByRole('link', { name: 'Item 1' })
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByRole('link', { name: 'Item 1' })
110 | await expect( overlayMenuFirstElement ).toBeHidden();
111 | await openMenuButton.click();
> 112 | await expect( overlayMenuFirstElement ).toBeVisible();
| ^
113 |
114 | // Test: overlay menu focuses on first element after opening
115 | await expect( overlayMenuFirstElement ).toBeFocused();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:112:44
|
|
[chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:169:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions:
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L197
3) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:169:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByRole('link', { name: 'Simple Submenu Link 1' })
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByRole('link', { name: 'Simple Submenu Link 1' })
195 | await simpleSubmenuButton.click();
196 | await expect( simpleSubmenuButton ).toBeFocused();
> 197 | await expect( innerElement ).toBeVisible();
| ^
198 |
199 | // Test: submenu closes on click outside submenu
200 | await page.click( 'body' );
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:197:33
|
|
[chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:169:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions:
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L197
3) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:169:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByRole('link', { name: 'Simple Submenu Link 1' })
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByRole('link', { name: 'Simple Submenu Link 1' })
195 | await simpleSubmenuButton.click();
196 | await expect( simpleSubmenuButton ).toBeFocused();
> 197 | await expect( innerElement ).toBeVisible();
| ^
198 |
199 | // Test: submenu closes on click outside submenu
200 | await page.click( 'body' );
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:197:33
|
|
[chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:169:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions:
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L197
3) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:169:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByRole('link', { name: 'Simple Submenu Link 1' })
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByRole('link', { name: 'Simple Submenu Link 1' })
195 | await simpleSubmenuButton.click();
196 | await expect( simpleSubmenuButton ).toBeFocused();
> 197 | await expect( innerElement ).toBeVisible();
| ^
198 |
199 | // Test: submenu closes on click outside submenu
200 | await page.click( 'body' );
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:197:33
|
|
[chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:268:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions on Safari (@webkit):
test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js#L296
4) [chromium] › editor/blocks/navigation-frontend-interactivity.spec.js:268:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions on Safari (@WebKit)
Error: Timed out 5000ms waiting for expect(locator).toBeVisible()
Locator: getByRole('link', { name: 'Simple Submenu Link 1' })
Expected: visible
Received: hidden
Call log:
- expect.toBeVisible with timeout 5000ms
- waiting for getByRole('link', { name: 'Simple Submenu Link 1' })
294 | await simpleSubmenuButton.click();
295 | await expect( simpleSubmenuButton ).toBeFocused();
> 296 | await expect( innerElement ).toBeVisible();
| ^
297 |
298 | // Test: a second click closes the submenu
299 | await simpleSubmenuButton.click();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/editor/blocks/navigation-frontend-interactivity.spec.js:296:33
|
|
[chromium] › interactivity/negation-operator.spec.ts:21:6 › negation-operator › add hidden attribute when !state.active:
test/e2e/specs/interactivity/negation-operator.spec.ts#L26
1) [chromium] › interactivity/negation-operator.spec.ts:21:6 › negation-operator › add hidden attribute when !state.active
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add hidden attribute if state is not active')
Expected string: ""
Received string: serializes to the same string
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add hidden attribute if state is not active')
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
24 | );
25 |
> 26 | await expect( el ).toHaveAttribute( 'hidden', '' );
| ^
27 | await page.getByTestId( 'toggle active value' ).click();
28 | await expect( el ).not.toHaveAttribute( 'hidden', '' );
29 | await page.getByTestId( 'toggle active value' ).click();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/negation-operator.spec.ts:26:22
|
|
[chromium] › interactivity/negation-operator.spec.ts:21:6 › negation-operator › add hidden attribute when !state.active:
test/e2e/specs/interactivity/negation-operator.spec.ts#L26
1) [chromium] › interactivity/negation-operator.spec.ts:21:6 › negation-operator › add hidden attribute when !state.active
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add hidden attribute if state is not active')
Expected string: ""
Received string: serializes to the same string
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add hidden attribute if state is not active')
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
24 | );
25 |
> 26 | await expect( el ).toHaveAttribute( 'hidden', '' );
| ^
27 | await page.getByTestId( 'toggle active value' ).click();
28 | await expect( el ).not.toHaveAttribute( 'hidden', '' );
29 | await page.getByTestId( 'toggle active value' ).click();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/negation-operator.spec.ts:26:22
|
|
[chromium] › interactivity/negation-operator.spec.ts:21:6 › negation-operator › add hidden attribute when !state.active:
test/e2e/specs/interactivity/negation-operator.spec.ts#L26
1) [chromium] › interactivity/negation-operator.spec.ts:21:6 › negation-operator › add hidden attribute when !state.active
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add hidden attribute if state is not active')
Expected string: ""
Received string: serializes to the same string
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add hidden attribute if state is not active')
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.active" data-testid…></div>
- unexpected value "null"
24 | );
25 |
> 26 | await expect( el ).toHaveAttribute( 'hidden', '' );
| ^
27 | await page.getByTestId( 'toggle active value' ).click();
28 | await expect( el ).not.toHaveAttribute( 'hidden', '' );
29 | await page.getByTestId( 'toggle active value' ).click();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/negation-operator.spec.ts:26:22
|
|
[chromium] › interactivity/negation-operator.spec.ts:33:6 › negation-operator › add hidden attribute when !selectors.active:
test/e2e/specs/interactivity/negation-operator.spec.ts#L38
2) [chromium] › interactivity/negation-operator.spec.ts:33:6 › negation-operator › add hidden attribute when !selectors.active
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add hidden attribute if selector is not active')
Expected string: ""
Received string: serializes to the same string
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add hidden attribute if selector is not active')
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
36 | );
37 |
> 38 | await expect( el ).toHaveAttribute( 'hidden', '' );
| ^
39 | await page.getByTestId( 'toggle active value' ).click();
40 | await expect( el ).not.toHaveAttribute( 'hidden', '' );
41 | await page.getByTestId( 'toggle active value' ).click();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/negation-operator.spec.ts:38:22
|
|
[chromium] › interactivity/negation-operator.spec.ts:33:6 › negation-operator › add hidden attribute when !selectors.active:
test/e2e/specs/interactivity/negation-operator.spec.ts#L38
2) [chromium] › interactivity/negation-operator.spec.ts:33:6 › negation-operator › add hidden attribute when !selectors.active
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add hidden attribute if selector is not active')
Expected string: ""
Received string: serializes to the same string
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add hidden attribute if selector is not active')
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
36 | );
37 |
> 38 | await expect( el ).toHaveAttribute( 'hidden', '' );
| ^
39 | await page.getByTestId( 'toggle active value' ).click();
40 | await expect( el ).not.toHaveAttribute( 'hidden', '' );
41 | await page.getByTestId( 'toggle active value' ).click();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/negation-operator.spec.ts:38:22
|
|
[chromium] › interactivity/negation-operator.spec.ts:33:6 › negation-operator › add hidden attribute when !selectors.active:
test/e2e/specs/interactivity/negation-operator.spec.ts#L38
2) [chromium] › interactivity/negation-operator.spec.ts:33:6 › negation-operator › add hidden attribute when !selectors.active
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add hidden attribute if selector is not active')
Expected string: ""
Received string: serializes to the same string
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add hidden attribute if selector is not active')
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
- locator resolved to <div data-wp-bind--hidden="!state.isActive" data-test…></div>
- unexpected value "null"
36 | );
37 |
> 38 | await expect( el ).toHaveAttribute( 'hidden', '' );
| ^
39 | await page.getByTestId( 'toggle active value' ).click();
40 | await expect( el ).not.toHaveAttribute( 'hidden', '' );
41 | await page.getByTestId( 'toggle active value' ).click();
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/negation-operator.spec.ts:38:22
|
|
[chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation:
test/e2e/specs/interactivity/router-navigate.spec.ts#L70
3) [chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation
Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected)
Locator: getByTestId('router navigations pending')
Expected string: "0"
Received string: "NaN"
Call log:
- expect.toHaveText with timeout 5000ms
- waiting for getByTestId('router navigations pending')
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
68 | const title = page.getByTestId( 'title' );
69 |
> 70 | await expect( navigations ).toHaveText( '0' );
| ^
71 | await expect( status ).toHaveText( 'idle' );
72 |
73 | let resolveLink1: Function;
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:70:31
|
|
[chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation:
test/e2e/specs/interactivity/router-navigate.spec.ts#L70
3) [chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected)
Locator: getByTestId('router navigations pending')
Expected string: "0"
Received string: "NaN"
Call log:
- expect.toHaveText with timeout 5000ms
- waiting for getByTestId('router navigations pending')
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
68 | const title = page.getByTestId( 'title' );
69 |
> 70 | await expect( navigations ).toHaveText( '0' );
| ^
71 | await expect( status ).toHaveText( 'idle' );
72 |
73 | let resolveLink1: Function;
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:70:31
|
|
[chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation:
test/e2e/specs/interactivity/router-navigate.spec.ts#L70
3) [chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected)
Locator: getByTestId('router navigations pending')
Expected string: "0"
Received string: "NaN"
Call log:
- expect.toHaveText with timeout 5000ms
- waiting for getByTestId('router navigations pending')
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
68 | const title = page.getByTestId( 'title' );
69 |
> 70 | await expect( navigations ).toHaveText( '0' );
| ^
71 | await expect( status ).toHaveText( 'idle' );
72 |
73 | let resolveLink1: Function;
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:70:31
|
|
[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:
test/e2e/specs/interactivity/router-navigate.spec.ts#L115
4) [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
Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected)
Locator: getByTestId('router navigations pending')
Expected string: "0"
Received string: "NaN"
Call log:
- expect.toHaveText with timeout 5000ms
- waiting for getByTestId('router navigations pending')
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
- locator resolved to <output data-testid="router navigations pending" data-wp…>NaN</output>
- unexpected value "NaN"
113 | const title = page.getByTestId( 'title' );
114 |
> 115 | await expect( navigations ).toHaveText( '0' );
| ^
116 | await expect( status ).toHaveText( 'idle' );
117 |
118 | const resolvers: Function[] = [];
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/router-navigate.spec.ts:115:31
|
|
[chromium] › interactivity/async-actions.spec.ts:19:6 › async actions › Promise generator callbacks should restore scope on resolve and reject:
test/e2e/specs/interactivity/async-actions.spec.ts#L26
1) [chromium] › interactivity/async-actions.spec.ts:19:6 › async actions › Promise generator callbacks should restore scope on resolve and reject
Error: Timed out 5000ms waiting for expect(locator).toHaveValue(expected)
Locator: getByTestId('result')
Expected string: "ok"
Received string: ""
Call log:
- expect.toHaveValue with timeout 5000ms
- waiting for getByTestId('result')
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
24 |
25 | await page.getByTestId( 'resolve' ).click();
> 26 | await expect( resultInput ).toHaveValue( 'ok' );
| ^
27 |
28 | await page.getByTestId( 'reject' ).click();
29 | await expect( resultInput ).toHaveValue( 'Error: 😘' );
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/async-actions.spec.ts:26:31
|
|
[chromium] › interactivity/async-actions.spec.ts:19:6 › async actions › Promise generator callbacks should restore scope on resolve and reject:
test/e2e/specs/interactivity/async-actions.spec.ts#L26
1) [chromium] › interactivity/async-actions.spec.ts:19:6 › async actions › Promise generator callbacks should restore scope on resolve and reject
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveValue(expected)
Locator: getByTestId('result')
Expected string: "ok"
Received string: ""
Call log:
- expect.toHaveValue with timeout 5000ms
- waiting for getByTestId('result')
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
24 |
25 | await page.getByTestId( 'resolve' ).click();
> 26 | await expect( resultInput ).toHaveValue( 'ok' );
| ^
27 |
28 | await page.getByTestId( 'reject' ).click();
29 | await expect( resultInput ).toHaveValue( 'Error: 😘' );
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/async-actions.spec.ts:26:31
|
|
[chromium] › interactivity/async-actions.spec.ts:19:6 › async actions › Promise generator callbacks should restore scope on resolve and reject:
test/e2e/specs/interactivity/async-actions.spec.ts#L26
1) [chromium] › interactivity/async-actions.spec.ts:19:6 › async actions › Promise generator callbacks should restore scope on resolve and reject
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveValue(expected)
Locator: getByTestId('result')
Expected string: "ok"
Received string: ""
Call log:
- expect.toHaveValue with timeout 5000ms
- waiting for getByTestId('result')
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
- locator resolved to <input readonly data-testid="result" data-wp-bind--valu…/>
- unexpected value ""
24 |
25 | await page.getByTestId( 'resolve' ).click();
> 26 | await expect( resultInput ).toHaveValue( 'ok' );
| ^
27 |
28 | await page.getByTestId( 'reject' ).click();
29 | await expect( resultInput ).toHaveValue( 'Error: 😘' );
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/async-actions.spec.ts:26:31
|
|
[chromium] › interactivity/deferred-store.spec.ts:19:6 › deferred store › Ensure that a store can be subscribed to before it is initialized:
test/e2e/specs/interactivity/deferred-store.spec.ts#L24
2) [chromium] › interactivity/deferred-store.spec.ts:19:6 › deferred store › Ensure that a store can be subscribed to before it is initialized
Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected)
Locator: getByTestId('result')
Expected string: "Hello, world!"
Received string: ""
Call log:
- expect.toHaveText with timeout 5000ms
- waiting for getByTestId('result')
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
22 | const resultInput = page.getByTestId( 'result' );
23 | await expect( resultInput ).toHaveText( '' );
> 24 | await expect( resultInput ).toHaveText( 'Hello, world!' );
| ^
25 | } );
26 |
27 | // There is a known issue for deferred getters right now.
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/deferred-store.spec.ts:24:31
|
|
[chromium] › interactivity/deferred-store.spec.ts:19:6 › deferred store › Ensure that a store can be subscribed to before it is initialized:
test/e2e/specs/interactivity/deferred-store.spec.ts#L24
2) [chromium] › interactivity/deferred-store.spec.ts:19:6 › deferred store › Ensure that a store can be subscribed to before it is initialized
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected)
Locator: getByTestId('result')
Expected string: "Hello, world!"
Received string: ""
Call log:
- expect.toHaveText with timeout 5000ms
- waiting for getByTestId('result')
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
22 | const resultInput = page.getByTestId( 'result' );
23 | await expect( resultInput ).toHaveText( '' );
> 24 | await expect( resultInput ).toHaveText( 'Hello, world!' );
| ^
25 | } );
26 |
27 | // There is a known issue for deferred getters right now.
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/deferred-store.spec.ts:24:31
|
|
[chromium] › interactivity/deferred-store.spec.ts:19:6 › deferred store › Ensure that a store can be subscribed to before it is initialized:
test/e2e/specs/interactivity/deferred-store.spec.ts#L24
2) [chromium] › interactivity/deferred-store.spec.ts:19:6 › deferred store › Ensure that a store can be subscribed to before it is initialized
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveText(expected)
Locator: getByTestId('result')
Expected string: "Hello, world!"
Received string: ""
Call log:
- expect.toHaveText with timeout 5000ms
- waiting for getByTestId('result')
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
- locator resolved to <span data-testid="result" data-wp-text="state.reverse…></span>
- unexpected value ""
22 | const resultInput = page.getByTestId( 'result' );
23 | await expect( resultInput ).toHaveText( '' );
> 24 | await expect( resultInput ).toHaveText( 'Hello, world!' );
| ^
25 | } );
26 |
27 | // There is a known issue for deferred getters right now.
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/deferred-store.spec.ts:24:31
|
|
[chromium] › interactivity/directive-bind.spec.ts:21:6 › data-wp-bind › add missing href at hydration:
test/e2e/specs/interactivity/directive-bind.spec.ts#L23
3) [chromium] › interactivity/directive-bind.spec.ts:21:6 › data-wp-bind › add missing href at hydration
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add missing href at hydration')
Expected string: "/some-url"
Received string: ""
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add missing href at hydration')
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
21 | test( 'add missing href at hydration', async ( { page } ) => {
22 | const el = page.getByTestId( 'add missing href at hydration' );
> 23 | await expect( el ).toHaveAttribute( 'href', '/some-url' );
| ^
24 | } );
25 |
26 | test( 'change href at hydration', async ( { page } ) => {
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:23:22
|
|
[chromium] › interactivity/directive-bind.spec.ts:21:6 › data-wp-bind › add missing href at hydration:
test/e2e/specs/interactivity/directive-bind.spec.ts#L23
3) [chromium] › interactivity/directive-bind.spec.ts:21:6 › data-wp-bind › add missing href at hydration
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add missing href at hydration')
Expected string: "/some-url"
Received string: ""
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add missing href at hydration')
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
21 | test( 'add missing href at hydration', async ( { page } ) => {
22 | const el = page.getByTestId( 'add missing href at hydration' );
> 23 | await expect( el ).toHaveAttribute( 'href', '/some-url' );
| ^
24 | } );
25 |
26 | test( 'change href at hydration', async ( { page } ) => {
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:23:22
|
|
[chromium] › interactivity/directive-bind.spec.ts:21:6 › data-wp-bind › add missing href at hydration:
test/e2e/specs/interactivity/directive-bind.spec.ts#L23
3) [chromium] › interactivity/directive-bind.spec.ts:21:6 › data-wp-bind › add missing href at hydration
Retry #2 ───────────────────────────────────────────────────────────────────────────────────────
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('add missing href at hydration')
Expected string: "/some-url"
Received string: ""
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('add missing href at hydration')
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
- locator resolved to <a data-wp-bind--href="state.url" data-testid="add …></a>
- unexpected value "null"
21 | test( 'add missing href at hydration', async ( { page } ) => {
22 | const el = page.getByTestId( 'add missing href at hydration' );
> 23 | await expect( el ).toHaveAttribute( 'href', '/some-url' );
| ^
24 | } );
25 |
26 | test( 'change href at hydration', async ( { page } ) => {
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:23:22
|
|
[chromium] › interactivity/directive-bind.spec.ts:26:6 › data-wp-bind › change href at hydration:
test/e2e/specs/interactivity/directive-bind.spec.ts#L28
4) [chromium] › interactivity/directive-bind.spec.ts:26:6 › data-wp-bind › change href at hydration
Error: Timed out 5000ms waiting for expect(locator).toHaveAttribute(expected)
Locator: getByTestId('change href at hydration')
Expected string: "/some-url"
Received string: "/other-url"
Call log:
- expect.toHaveAttribute with timeout 5000ms
- waiting for getByTestId('change href at hydration')
- locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a>
- unexpected value "/other-url"
- locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a>
- unexpected value "/other-url"
- locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a>
- unexpected value "/other-url"
- locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a>
- unexpected value "/other-url"
- locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a>
- unexpected value "/other-url"
- locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a>
- unexpected value "/other-url"
- locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a>
- unexpected value "/other-url"
- locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a>
- unexpected value "/other-url"
- locator resolved to <a href="/other-url" data-wp-bind--href="state.url"…></a>
- unexpected value "/other-url"
26 | test( 'change href at hydration', async ( { page } ) => {
27 | const el = page.getByTestId( 'change href at hydration' );
> 28 | await expect( el ).toHaveAttribute( 'href', '/some-url' );
| ^
29 | } );
30 |
31 | test( 'update missing href at hydration', async ( { page } ) => {
at /home/runner/work/gutenberg/gutenberg/test/e2e/specs/interactivity/directive-bind.spec.ts:28:22
|
|
Merge Artifacts
No artifacts found matching pattern 'flaky-tests-report*'
|
|
🎭 Playwright Run Summary
182 passed (8.4m)
|
|
🎭 Playwright Run Summary
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
144 passed (8.9m)
|
|
🎭 Playwright Run Summary
1 skipped
188 passed (9.5m)
|
|
🎭 Playwright Run Summary
1 skipped
188 passed (10.0m)
|
|
🎭 Playwright Run Summary
5 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
185 passed (12.0m)
|
|
🎭 Playwright Run Summary
6 failed
[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
184 passed (12.0m)
|
|
🎭 Playwright Run Summary
29 failed
[chromium] › interactivity/negation-operator.spec.ts:21:6 › negation-operator › add hidden attribute when !state.active
[chromium] › interactivity/negation-operator.spec.ts:33:6 › negation-operator › add hidden attribute when !selectors.active
[chromium] › interactivity/router-navigate.spec.ts:59:6 › Router navigate › should update the HTML only for the latest navigation
[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
[chromium] › interactivity/router-navigate.spec.ts:151:6 › Router navigate › should reload the next page when the timeout ends
[chromium] › interactivity/router-navigate.spec.ts:191:6 › Router navigate › should force a page reload when the `clientNavigationDisabled` config is set to true
[chromium] › interactivity/router-navigate.spec.ts:214:6 › Router navigate › should overwrite the state with the one serialized in the new page
[chromium] › interactivity/router-navigate.spec.ts:242:6 › Router navigate › should not try to overwrite getters with values from the initial data
[chromium] › interactivity/router-navigate.spec.ts:270:6 › Router navigate › should force a page reload when navigating to a page with `clientNavigationDisabled`
[chromium] › interactivity/router-regions.spec.ts:28:6 › Router regions › should be the only part hydrated
[chromium] › interactivity/router-regions.spec.ts:40:6 › Router regions › should update after navigation
[chromium] › interactivity/router-regions.spec.ts:58:6 › Router regions › should preserve state across pages
[chromium] › interactivity/router-regions.spec.ts:74:6 › Router regions › should preserve context across pages
[chromium] › interactivity/router-regions.spec.ts:90:6 › Router regions › can be nested ────────
[chromium] › interactivity/router-regions.spec.ts:101:6 › Router regions › Page title is updated 2
[chromium] › interactivity/store.spec.ts:21:6 › store › non-plain objects are not proxified ────
[chromium] › interactivity/store.spec.ts:26:6 › store › Ensures that state cannot be set to a non-object
[chromium] › interactivity/tovdom-islands.spec.ts:26:6 › toVdom - islands › directives that are inside islands with json objects should be hydrated
[chromium] › interactivity/tovdom-islands.spec.ts:33:6 › toVdom - islands › directives that are inside islands with strings should be hydrated
[chromium] › interactivity/tovdom-islands.spec.ts:49:6 › toVdom - islands › directives inside islands should not be hydrated twice
[chromium] › interactivity/tovdom-islands.spec.ts:57:6 › toVdom - islands › islands inside inner blocks of isolated islands should be hydrated
[chromium] › interactivity/tovdom-islands.spec.ts:66:6 › toVdom - islands › islands should recover their namespace if an inner island has changed it
[chromium] › interactivity/tovdom.spec.ts:19:6 › toVdom › it should delete comments ────────────
[chromium] › interactivity/tovdom.spec.ts:30:6 › toVdom › it should delete processing instructions
[chromium] › interactivity/with-scope.spec.ts:19:6 › withScope › directives using withScope should work with async and sync functions
[webkit] › editor/blocks/navigation-frontend-interactivity.spec.js:93:3 › Navigation block - Frontend interactivity › Overlay menu › Overlay menu interactions in Safari (@WebKit)
[webkit] › editor/blocks/navigation-frontend-interactivity.spec.js:268:3 › Navigation block - Frontend interactivity › Submenu mouse and keyboard interactions › Submenu interactions on Safari (@WebKit)
[webkit] › editor/blocks/navigation-frontend-interactivity.spec.js:378:3 › Navigation block - Frontend interactivity › Submenus (Arrow setting) (@Firefox, @WebKit) › submenu click on the arrow interactions
[webkit] › editor/blocks/navigation-frontend-interactivity.spec.js:470:3 › Navigation block - Frontend interactivity › Page list block (@Firefox, @WebKit) › page-list submenu user interactions
193 passed
|
|
🎭 Playwright Run Summary
109 failed
[chromium] › interactivity/async-actions.spec.ts:19:6 › async actions › Promise generator callbacks should restore scope on resolve and reject
[chromium] › interactivity/deferred-store.spec.ts:19:6 › deferred store › Ensure that a store can be subscribed to before it is initialized
[chromium] › interactivity/directive-bind.spec.ts:21:6 › data-wp-bind › add missing href at hydration
[chromium] › interactivity/directive-bind.spec.ts:26:6 › data-wp-bind › change href at hydration
[chromium] › interactivity/directive-bind.spec.ts:31:6 › data-wp-bind › update missing href at hydration
[chromium] › interactivity/directive-bind.spec.ts:38:6 › data-wp-bind › add missing checked at hydration
[chromium] › interactivity/directive-bind.spec.ts:43:6 › data-wp-bind › remove existing checked at hydration
[chromium] › interactivity/directive-bind.spec.ts:48:6 › data-wp-bind › update existing checked
[chromium] › interactivity/directive-bind.spec.ts:70:6 › data-wp-bind › nested binds ───────────
[chromium] › interactivity/directive-bind.spec.ts:80:6 › data-wp-bind › check enumerated attributes with true/false values
[chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › width is correctly hydrated for different values
[chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › name is correctly hydrated for different values
[chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › value is correctly hydrated for different values
[chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › disabled is correctly hydrated for different values
[chromium] › interactivity/directive-bind.spec.ts:203:8 › data-wp-bind › attribute hydration › aria-disabled 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:34:6 › data-wp-class › add class if callback returns truthy value
[chromium] › interactivity/directive-class.spec.ts:45:6 › data-wp-class › handles multiple classes and callbacks
[chromium] › interactivity/directive-class.spec.ts:58:6 › data-wp-class › handles class names that are contained inside other class names
[chromium] › interactivity/directive-class.spec.ts:71:6 › data-wp-class › can toggle class in the middle
[chromium] › interactivity/directive-class.spec.ts:80:6 › data-wp-class › can toggle class when class attribute is missing
[chromium] › interactivity/directive-class.spec.ts:93:6 › data-wp-class › can use context values
[chromium] › interactivity/directive-class.spec.ts:102:6 › data-wp-class › can use BEM notation classes
[chromium] › interactivity/directive-class.spec.ts:107:6 › data-wp-class › can use classes with several dashes
[chromium] › interactivity/directive-context.spec.ts:28:6 › data-wp-context › is correctly initialized
[chromium] › interactivity/directive-context.spec.ts:41:6 › data-wp-context › is correctly extended
[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:160:6 › data-wp-context › Array properties are shadowed
[chromium] › interactivity/directive-context.spec.ts:173:6 › data-wp-context › over
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
failures-artifacts
Expired
|
186 MB |
|