1) tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render fan.stl without error Test timeout of 60000ms exceeded.

1) tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render fan.stl without error Error: locator.click: Test timeout of 60000ms exceeded. Call log: - waiting for getByRole('tablist', { name: 'main sidebar' }).getByRole('tab', { name: 'JupyterCad Control Panel' }) - locator resolved to <li role="tab" tabindex="-1" id="tab-key-1-6" aria-selected="true" title="JupyterCad Control Panel" class="lm-TabBar-tab lm-mod-current" data-id="jupytercad::leftControlPanel">…</li> - 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 - <dialog aria-modal="true" class="lm-Widget jp-Dialog" aria-label="File Load Error for fan.stl Unexpected token 's', "solid CATI"... is not valid JSON">…</dialog> intercepts pointer events - retrying click action, attempt #1 - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <dialog aria-modal="true" class="lm-Widget jp-Dialog" aria-label="File Load Error for fan.stl Unexpected token 's', "solid CATI"... is not valid JSON">…</dialog> intercepts pointer events - retrying click action, attempt #2 - waiting 20ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <dialog aria-modal="true" class="lm-Widget jp-Dialog" aria-label="File Load Error for fan.stl Unexpected token 's', "solid CATI"... is not valid JSON">…</dialog> intercepts pointer events - retrying click action, attempt #3 - waiting 100ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <dialog aria-modal="true" class="lm-Widget jp-Dialog" aria-label="File Load Error for fan.stl Unexpected token 's', "solid CATI"... is not valid JSON">…</dialog> intercepts pointer events - retrying click action, attempt #4 - waiting 100ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <dialog aria-modal="true" class="lm-Widget jp-Dialog" aria-label="File Load Error for fan.stl Unexpected token 's', "solid CATI"... is not valid JSON">…</dialog> intercepts pointer events - retrying click action, attempt #5 - waiting 500ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <dialog aria-modal="true" class="lm-Widget jp-Dialog" aria-label="File Load Error for fan.stl Unexpected token 's', "solid CATI"... is not valid JSON">…</dialog> intercepts pointer events - retrying click action, attempt #6 - waiting 500ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <dialog aria-modal="true" class="lm-Widget jp-Dialog" aria-label="File Load Error for fan.stl Unexpected token 's', "solid CATI"... is not valid JSON">…</dialog> intercepts pointer events - retrying click action, attempt #7 - waiting 500ms - waiting for element to be visible, enabled and stable - element is visible, enabled and stable - scrolling into view if needed - done scrolling - <dialog aria-modal="true" class="lm-Widget jp-Dialog" aria-label="File Load Error for fan.stl Unexpected token 's', "solid CATI"... is not valid JSON">…</dialog> intercepts pointer events - retrying click action, attempt #8 - waiting 500ms - waiting for element to be vi

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. 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 uses node12 which is deprecated and will be forced to run on node16: actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v2, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4, actions/download-artifact@v3. 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/checkout@v3, actions/download-artifact@v3. 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/checkout@v3, actions/download-artifact@v3, actions/cache@v3. 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: "extension-artifacts". 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/