1) [chromium] › jupyterlab_ui_tests/jupyterlab.mitosheet.spec.ts:14:7 › Mitosheet JupyterLab integration › Can run the generated code Test timeout of 60000ms exceeded.

1) [chromium] › jupyterlab_ui_tests/jupyterlab.mitosheet.spec.ts:14:7 › Mitosheet JupyterLab integration › Can run the generated code Error: proxy.waitForTimeout: Test timeout of 60000ms exceeded. at jupyterlab_ui_tests/utils.ts:59 57 | while (!/[a-zA-Z]/g.test(cellCode || '')) { 58 | // Wait 20 ms > 59 | await page.waitForTimeout(20); | ^ 60 | await waitForIdle(page); 61 | const cellInput = await page.notebook.getCellInput(cellIndex); 62 | cellCode = (await cellInput?.innerText())?.trim(); at waitForCodeToBeWritten (/home/runner/work/mito/mito/tests/jupyterlab_ui_tests/utils.ts:59:16) at /home/runner/work/mito/mito/tests/jupyterlab_ui_tests/jupyterlab.mitosheet.spec.ts:20:5

The following actions uses node12 which is deprecated and will be forced to run on node16: styfle/cancel-workflow-action@0.7.0, actions/checkout@v2, actions/setup-python@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: styfle/cancel-workflow-action@0.7.0, actions/checkout@v2, actions/setup-python@v2, actions/setup-node@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: "test-results-grid-macos-latest-python3.10-firefox". 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/