2) [Integration Tests] › ../../../../../../../runner/_work/enso/enso/app/gui/integration-test/project-view/widgets.spec.ts:1025:1 › Table widget Error: expect(locator).toHaveText(expected) failed Locator: locator('.GraphNode').filter({ has: locator('.binding').getByText('any1', { exact: true }) }).locator('.WidgetTableEditor').locator('.ag-header-cell-text') - Expected - 1 + Received + 1 Array [ "#", - "Header", + "Column 1", ] Call log: - Expect "toHaveText" with timeout 25000ms - waiting for locator('.GraphNode').filter({ has: locator('.binding').getByText('any1', { exact: true }) }).locator('.WidgetTableEditor').locator('.ag-header-cell-text') 24 × locator resolved to 2 elements 1049 | await page.keyboard.type('Header') 1050 | await page.keyboard.press('Enter') > 1051 | await expect(widget.locator('.ag-header-cell-text')).toHaveText(['#', 'Header']) | ^ 1052 | 1053 | // Adding next column 1054 | await widget.getByRole('button', { name: 'Add new column' }).click() at /runner/_work/enso/enso/app/gui/integration-test/project-view/widgets.spec.ts:1051:56

2) [Integration Tests] › ../../../../../../../runner/_work/enso/enso/app/gui/integration-test/project-view/widgets.spec.ts:1025:1 › Table widget Test timeout of 25000ms exceeded.

1) [Integration Tests] › ../../../../../../../runner/_work/enso/enso/app/gui/integration-test/dashboard/editAssetName.spec.ts:167:3 › edit name, error message is visible Error: locator.click: Test timeout of 25000ms exceeded. Call log: - waiting for getByTestId('context-menu').getByText(/Rename/) - locator resolved to <span id=":r1lg:" slot="label" class="text-primary text-xs leading-[20px] before:h-[2px] after:h-[2px] macos:before:h-[1px] macos:after:h-[3px] flex-col before:block after:block before:flex-none after:flex-none before:w-full after:w-full font-medium">Rename</span> - 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 - element was detached from the DOM, retrying 174 | await locateContextMenu(page) 175 | .getByText(/Rename/) > 176 | .click() | ^ 177 | 178 | const inputEl = locateInput(nameEl) 179 | at /runner/_work/enso/enso/app/gui/integration-test/dashboard/editAssetName.spec.ts:176:10 at /runner/_work/enso/enso/app/gui/integration-test/actions/DrivePageActions.ts:217:11 at /runner/_work/enso/enso/app/gui/integration-test/actions/BaseActions.ts:186:21 at /runner/_work/enso/enso/app/gui/integration-test/actions/BaseActions.ts:184:14

1) [Integration Tests] › ../../../../../../../runner/_work/enso/enso/app/gui/integration-test/dashboard/editAssetName.spec.ts:167:3 › edit name, error message is visible Error: locator.click: Test timeout of 25000ms exceeded. Call log: - waiting for getByTestId('context-menu').getByText(/Rename/) - locator resolved to <span id=":r1lg:" slot="label" class="text-primary text-xs leading-[20px] before:h-[2px] after:h-[2px] macos:before:h-[1px] macos:after:h-[3px] flex-col before:block after:block before:flex-none after:flex-none before:w-full after:w-full font-medium">Rename</span> - 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 - element was detached from the DOM, retrying 174 | await locateContextMenu(page) 175 | .getByText(/Rename/) > 176 | .click() | ^ 177 | 178 | const inputEl = locateInput(nameEl) 179 | at /runner/_work/enso/enso/app/gui/integration-test/dashboard/editAssetName.spec.ts:176:10 at /runner/_work/enso/enso/app/gui/integration-test/actions/DrivePageActions.ts:217:11 at /runner/_work/enso/enso/app/gui/integration-test/actions/BaseActions.ts:186:21 at /runner/_work/enso/enso/app/gui/integration-test/actions/BaseActions.ts:184:14

1) [Integration Tests] › ../../../../../../../runner/_work/enso/enso/app/gui/integration-test/dashboard/editAssetName.spec.ts:167:3 › edit name, error message is visible Test timeout of 25000ms exceeded.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, step-security/changed-files@v45. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, bazel-contrib/setup-bazel@0.15.0, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, bazel-contrib/setup-bazel@0.15.0, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, bazel-contrib/setup-bazel@0.15.0, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/checkout@v4, actions/setup-node@v4, bazel-contrib/setup-bazel@0.15.0, enso-org/eslint-annotate-action@v3, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, bazel-contrib/setup-bazel@0.15.0, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/upload-artifact@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/