1) [chromium] › tests/kit/input-date-range/input-date-range.spec.ts:139:13 › InputDateRange › API › Select from [items] => select date range from calendar Error: Timed out 5000ms waiting for expect(locator).toHaveValue(expected) Locator: locator('#demo-content').locator('tui-input-date-range').getByRole('textbox') Expected string: "21.09.2020 – 25.09.2020" Received string: "Today" Call log: - expect.toHaveValue with timeout 5000ms - waiting for locator('#demo-content').locator('tui-input-date-range').getByRole('textbox') - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" 154 | await calendar.clickOnCalendarDay(21); 155 | > 156 | await expect(inputDateRange.textfield).toHaveValue( | ^ 157 | `21.09.2020${CHAR_NO_BREAK_SPACE}–${CHAR_NO_BREAK_SPACE}25.09.2020`, 158 | ); 159 | await expect(example).toHaveScreenshot( at /home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/tests/kit/input-date-range/input-date-range.spec.ts:156:52

1) [chromium] › tests/kit/input-date-range/input-date-range.spec.ts:139:13 › InputDateRange › API › Select from [items] => select date range from calendar Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Timed out 5000ms waiting for expect(locator).toHaveValue(expected) Locator: locator('#demo-content').locator('tui-input-date-range').getByRole('textbox') Expected string: "21.09.2020 – 25.09.2020" Received string: "Today" Call log: - expect.toHaveValue with timeout 5000ms - waiting for locator('#demo-content').locator('tui-input-date-range').getByRole('textbox') - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" - locator resolved to <input tabindex="0" placeholder="" tuimaskaccessor="" a…/> - unexpected value "Today" 154 | await calendar.clickOnCalendarDay(21); 155 | > 156 | await expect(inputDateRange.textfield).toHaveValue( | ^ 157 | `21.09.2020${CHAR_NO_BREAK_SPACE}–${CHAR_NO_BREAK_SPACE}25.09.2020`, 158 | ); 159 | await expect(example).toHaveScreenshot( at /home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/tests/kit/input-date-range/input-date-range.spec.ts:156:52

2) [chromium] › tests/kit/input-date-range/input-date-range.spec.ts:195:13 › InputDateRange › Examples › Select second same range => after close/open calendar displays selected period displays correctly Test timeout of 30000ms exceeded.

2) [chromium] › tests/kit/input-date-range/input-date-range.spec.ts:195:13 › InputDateRange › Examples › Select second same range => after close/open calendar displays selected period displays correctly Error: locator.click: Test timeout of 30000ms exceeded. Call log: - waiting for locator('tui-calendar-range').locator('[automation-id="tui-calendar-range__menu"]').locator('[tuiOption]').nth(2) - locator resolved to <button tuioption="" tabindex="-1" type="button" role="m…>…</button> - attempting click action - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - performing click action - <div _ngcontent-tui-demo-c345="" class="t-content t-c…>…</div> from <div class="t-root-content">…</div> subtree intercepts pointer events - retrying click action, attempt #1 - waiting for element to be visible, enabled and stable - element was detached from the DOM, retrying at utils/page-objects/input-date-range.po.ts:25 23 | const items = await this.getItems(); 24 | > 25 | await items[index].click(); | ^ 26 | } 27 | 28 | async itemHasCheckmark(index: number): Promise<boolean> { at TuiInputDateRangePO.selectItem (/home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/utils/page-objects/input-date-range.po.ts:25:28) at /home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/tests/kit/input-date-range/input-date-range.spec.ts:203:13

2) [chromium] › tests/kit/input-date-range/input-date-range.spec.ts:195:13 › InputDateRange › Examples › Select second same range => after close/open calendar displays selected period displays correctly Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded.

2) [chromium] › tests/kit/input-date-range/input-date-range.spec.ts:195:13 › InputDateRange › Examples › Select second same range => after close/open calendar displays selected period displays correctly Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.click: Test timeout of 30000ms exceeded. Call log: - waiting for locator('tui-calendar-range').locator('[automation-id="tui-calendar-range__menu"]').locator('[tuiOption]').nth(2) - locator resolved to <button tuioption="" tabindex="-1" type="button" role="m…>…</button> - attempting click action - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - performing click action - <div _ngcontent-tui-demo-c345="" class="t-content t-c…>…</div> from <div class="t-root-content">…</div> subtree intercepts pointer events - retrying click action, attempt #1 - waiting for element to be visible, enabled and stable - element was detached from the DOM, retrying at utils/page-objects/input-date-range.po.ts:25 23 | const items = await this.getItems(); 24 | > 25 | await items[index].click(); | ^ 26 | } 27 | 28 | async itemHasCheckmark(index: number): Promise<boolean> { at TuiInputDateRangePO.selectItem (/home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/utils/page-objects/input-date-range.po.ts:25:28) at /home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/tests/kit/input-date-range/input-date-range.spec.ts:203:13

Process completed with exit code 1.

1) [chromium] › tests/demo/demo.spec.ts:10:13 › Demo › /components/calendar-range ──────────────── Error: Screenshot comparison failed: 17492 pixels (ratio 0.03 of all image pixels) are different. Expected: /home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/snapshots/tests/demo/demo.spec.ts-snapshots/components-calendar-range/2-chromium-linux.png Received: /home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/tests-results/tests-demo-demo-Demo-components-calendar-range-chromium/components-calendar-range/2-actual.png Diff: /home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/tests-results/tests-demo-demo-Demo-components-calendar-range-chromium/components-calendar-range/2-diff.png Call log: - page._expectScreenshot with timeout 5000ms - verifying given screenshot expectation - waiting for locator('tui-doc-example [automation-id="tui-doc-example"]').nth(1) - locator resolved to <div _ngcontent-tui-demo-c345="" automation-id="tui-d…>…</div> - taking element screenshot - disabled all CSS animations - waiting for element to be visible and stable - element is visible and stable - 17492 pixels (ratio 0.03 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('tui-doc-example [automation-id="tui-doc-example"]').nth(1) - locator resolved to <div _ngcontent-tui-demo-c345="" automation-id="tui-d…>…</div> - taking element screenshot - disabled all CSS animations - waiting for element to be visible and stable - element is visible and stable - captured a stable screenshot - 17492 pixels (ratio 0.03 of all image pixels) are different. 33 | } 34 | > 35 | await expect(example).toHaveScreenshot([ | ^ 36 | path.replace('/', '').replace(/\//g, '-'), 37 | `${i + 1}.png`, 38 | ]); at /home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/tests/demo/demo.spec.ts:35:39

1) [chromium] › tests/demo/demo.spec.ts:10:13 › Demo › /components/calendar-range ──────────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 17492 pixels (ratio 0.03 of all image pixels) are different. Expected: /home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/snapshots/tests/demo/demo.spec.ts-snapshots/components-calendar-range/2-chromium-linux.png Received: /home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/tests-results/tests-demo-demo-Demo-components-calendar-range-chromium-retry1/components-calendar-range/2-actual.png Diff: /home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/tests-results/tests-demo-demo-Demo-components-calendar-range-chromium-retry1/components-calendar-range/2-diff.png Call log: - page._expectScreenshot with timeout 5000ms - verifying given screenshot expectation - waiting for locator('tui-doc-example [automation-id="tui-doc-example"]').nth(1) - locator resolved to <div _ngcontent-tui-demo-c345="" automation-id="tui-d…>…</div> - taking element screenshot - disabled all CSS animations - waiting for element to be visible and stable - element is visible and stable - 17492 pixels (ratio 0.03 of all image pixels) are different. - waiting 100ms before taking screenshot - waiting for locator('tui-doc-example [automation-id="tui-doc-example"]').nth(1) - locator resolved to <div _ngcontent-tui-demo-c345="" automation-id="tui-d…>…</div> - taking element screenshot - disabled all CSS animations - waiting for element to be visible and stable - element is visible and stable - captured a stable screenshot - 17492 pixels (ratio 0.03 of all image pixels) are different. 33 | } 34 | > 35 | await expect(example).toHaveScreenshot([ | ^ 36 | path.replace('/', '').replace(/\//g, '-'), 37 | `${i + 1}.png`, 38 | ]); at /home/runner/work/taiga-ui/taiga-ui/projects/demo-playwright/tests/demo/demo.spec.ts:35:39

Process completed with exit code 1.

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/cache/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/cache/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/cache/[email protected], actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/cache/[email protected], actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/cache/[email protected], actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/cache/[email protected], actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/cache/[email protected], actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/[email protected], actions/cache/[email protected], actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "cypress-e2e-artifacts--369e0af6666373785e0c5d7b2cf9c74b81a82755-10452416868-8595", "playwright-e2e-artifacts--369e0af6666373785e0c5d7b2cf9c74b81a82755-10452416868-8595". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

2 failed [chromium] › tests/kit/input-date-range/input-date-range.spec.ts:139:13 › InputDateRange › API › Select from [items] => select date range from calendar [chromium] › tests/kit/input-date-range/input-date-range.spec.ts:195:13 › InputDateRange › Examples › Select second same range => after close/open calendar displays selected period displays correctly 90 passed (2.3m)

92 passed (1.2m)

92 passed (1.4m)

93 passed (1.3m)

93 passed (1.1m)

93 passed (1.8m)