1) [chromium] › components/search/atomic-did-you-mean/e2e/atomic-did-you-mean.e2e.ts:74:3 › with a query trigger › should show trigger correction text Test timeout of 30000ms exceeded while running "beforeEach" hook. 63 | const ORIGINAL_QUERY = 'Japan'; 64 | const TRIGGER_QUERY = 'China'; > 65 | test.beforeEach(async ({didYouMean}) => { | ^ 66 | await didYouMean.load({story: 'query-trigger'}); 67 | await didYouMean.hydrated.waitFor(); 68 | }); at /home/runner/work/ui-kit/ui-kit/packages/atomic/src/components/search/atomic-did-you-mean/e2e/atomic-did-you-mean.e2e.ts:65:8

1) [chromium] › components/search/atomic-did-you-mean/e2e/atomic-did-you-mean.e2e.ts:74:3 › with a query trigger › should show trigger correction text Error: locator.waitFor: Test timeout of 30000ms exceeded. Call log: - waiting for locator('atomic-did-you-mean[class*="hydrated"]') to be visible - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query

1) [chromium] › components/search/tabs/atomic-tab-manager/e2e/atomic-tab-manager.e2e.ts:143:9 › AtomicTabManager › when viewport is large enough to display all tabs › when clicking on tab button › should change other component visibility › generated answer Test timeout of 30000ms exceeded.

1) [chromium] › components/search/tabs/atomic-tab-manager/e2e/atomic-tab-manager.e2e.ts:143:9 › AtomicTabManager › when viewport is large enough to display all tabs › when clicking on tab button › should change other component visibility › generated answer Error: locator.waitFor: Test timeout of 30000ms exceeded. Call log: - waiting for getByText('Generated answer', { exact: true }) to be visible 149 | await searchBox.searchInput.press('Enter'); 150 | > 151 | await tabManager.generatedAnswer.waitFor({state: 'visible'}); | ^ 152 | await expect(tabManager.generatedAnswer).toBeVisible(); 153 | }); 154 | }); at /home/runner/work/ui-kit/ui-kit/packages/atomic/src/components/search/tabs/atomic-tab-manager/e2e/atomic-tab-manager.e2e.ts:151:44

1) [chromium] › components/search/atomic-did-you-mean/e2e/atomic-did-you-mean.e2e.ts:47:3 › with a manual query correction › should show manual correction button Test timeout of 30000ms exceeded while running "beforeEach" hook. 30 | const ORIGINAL_QUERY = 'ceveo'; 31 | const CORRECTED_QUERY = 'coveo'; > 32 | test.beforeEach(async ({didYouMean}) => { | ^ 33 | await didYouMean.load({story: 'manual-correction'}); 34 | await didYouMean.hydrated.waitFor(); 35 | }); at /home/runner/work/ui-kit/ui-kit/packages/atomic/src/components/search/atomic-did-you-mean/e2e/atomic-did-you-mean.e2e.ts:32:8

1) [chromium] › components/search/atomic-did-you-mean/e2e/atomic-did-you-mean.e2e.ts:47:3 › with a manual query correction › should show manual correction button Error: locator.waitFor: Test timeout of 30000ms exceeded. Call log: - waiting for locator('atomic-did-you-mean[class*="hydrated"]') to be visible - locator resolved to hidden <atomic-did-you-mean data-atomic-loaded="false" data-atomic-rendered="false" query-correction-mode="next" class="atomic-hidden hydrated" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-a

2) [chromium] › components/search/atomic-did-you-mean/e2e/atomic-did-you-mean.e2e.ts:53:3 › with a manual query correction › when clicking on the manual correction button, the search box should contain the corrected query Test timeout of 30000ms exceeded while running "beforeEach" hook. 30 | const ORIGINAL_QUERY = 'ceveo'; 31 | const CORRECTED_QUERY = 'coveo'; > 32 | test.beforeEach(async ({didYouMean}) => { | ^ 33 | await didYouMean.load({story: 'manual-correction'}); 34 | await didYouMean.hydrated.waitFor(); 35 | }); at /home/runner/work/ui-kit/ui-kit/packages/atomic/src/components/search/atomic-did-you-mean/e2e/atomic-did-you-mean.e2e.ts:32:8

2) [chromium] › components/search/atomic-did-you-mean/e2e/atomic-did-you-mean.e2e.ts:53:3 › with a manual query correction › when clicking on the manual correction button, the search box should contain the corrected query Error: locator.waitFor: Test timeout of 30000ms exceeded. Call log: - waiting for locator('atomic-did-you-mean[class*="hydrated"]') to be visible - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class

2) [chromium] › components/search/atomic-did-you-mean/e2e/atomic-did-you-mean.e2e.ts:53:3 › with a manual query correction › when clicking on the manual correction button, the search box should contain the corrected query Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 30000ms exceeded while running "beforeEach" hook. 30 | const ORIGINAL_QUERY = 'ceveo'; 31 | const CORRECTED_QUERY = 'coveo'; > 32 | test.beforeEach(async ({didYouMean}) => { | ^ 33 | await didYouMean.load({story: 'manual-correction'}); 34 | await didYouMean.hydrated.waitFor(); 35 | }); at /home/runner/work/ui-kit/ui-kit/packages/atomic/src/components/search/atomic-did-you-mean/e2e/atomic-did-you-mean.e2e.ts:32:8

2) [chromium] › components/search/atomic-did-you-mean/e2e/atomic-did-you-mean.e2e.ts:53:3 › with a manual query correction › when clicking on the manual correction button, the search box should contain the corrected query Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.waitFor: Test timeout of 30000ms exceeded. Call log: - waiting for locator('atomic-did-you-mean[class*="hydrated"]') to be visible - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">↵ ↵ </atomic-did-you-mean> - locator resolved to hidden <atomic-did-you-mean class="hydrated" data-atomic-loaded="true" data-atomic-rendered="true" query-correction-mode="next" automatically-correct-query="">

The following actions use a deprecated Node.js version and will be forced to run on node20: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

packages/atomic/[chromium] › components/commerce/atomic-commerce-search-box/e2e/atomic-commerce-search-box.e2e.ts took 17.8s

packages/atomic/[chromium] › components/commerce/atomic-commerce-pager/e2e/atomic-commerce-pager.e2e.ts took 22.4s

packages/atomic/[chromium] › components/search/tabs/atomic-tab-manager/e2e/atomic-tab-manager.e2e.ts took 15.5s

packages/atomic/[chromium] › components/commerce/atomic-commerce-breadbox/e2e/atomic-commerce-breadbox.e2e.ts took 25.3s

packages/atomic/[chromium] › components/commerce/atomic-commerce-breadbox/e2e/atomic-commerce-breadbox.e2e.ts took 28.4s

packages/atomic/[chromium] › components/commerce/product-template-components/atomic-product-image/e2e/atomic-product-image.e2e.ts took 35.4s

packages/atomic/[chromium] › components/search/tabs/atomic-tab-manager/e2e/atomic-tab-manager.e2e.ts took 33.7s

packages/atomic/[chromium] › components/search/facets/atomic-facet/e2e/atomic-facet.e2e.ts took 20.2s

The following actions use a deprecated Node.js version and will be forced to run on node20: cypress-io/github-action@v5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

packages/atomic/[chromium] › components/commerce/product-template-components/atomic-product-image/e2e/atomic-product-image.e2e.ts took 15.7s

packages/atomic/[chromium] › components/commerce/atomic-commerce-breadbox/e2e/atomic-commerce-breadbox.e2e.ts took 19.4s

The following actions use a deprecated Node.js version and will be forced to run on node20: cypress-io/github-action@v5. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

packages/atomic/[chromium] › components/search/atomic-search-box/e2e/atomic-search-box.e2e.ts took 19.9s

The following actions use a deprecated Node.js version and will be forced to run on node20: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5, actions/upload-artifact@ff15f0306b3f739f7b6fd43fb5d26cd321bd4de5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: cypress-io/github-action@v5. 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: "result-lists-screenshots". 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/

17 passed (16.6s)

17 passed (19.1s)

18 passed (24.4s)

18 passed (21.0s)

18 passed (25.6s)

1 skipped 16 passed (26.3s)

18 passed (16.5s)

18 passed (28.5s)

17 passed (31.5s)

18 passed (38.6s)

18 passed (19.8s)

17 passed (37.0s)

17 passed (23.3s)

18 passed (28.4s)

18 passed (32.4s)

18 passed (36.1s)

1 flaky [chromium] › components/search/atomic-did-you-mean/e2e/atomic-did-you-mean.e2e.ts:74:3 › with a query trigger › should show trigger correction text 16 passed (55.4s)

18 passed (20.0s)

18 passed (24.2s)

18 passed (30.3s)

18 passed (29.6s)

18 passed (34.2s)

17 passed (23.2s)

1 flaky [chromium] › components/search/tabs/atomic-tab-manager/e2e/atomic-tab-manager.e2e.ts:143:9 › AtomicTabManager › when viewport is large enough to display all tabs › when clicking on tab button › should change other component visibility › generated answer 16 passed (1.1m)