Skip to content

Jupyter Collaboration v2 #1042

Jupyter Collaboration v2

Jupyter Collaboration v2 #1042

Triggered via pull request February 8, 2024 10:36
Status Failure
Total duration 9m 56s
Artifacts 2

build.yml

on: pull_request
Build jupytercad
5m 7s
Build jupytercad
Check Links
57s
Check Links
test_isolated
25s
test_isolated
Integration tests
4m 34s
Integration tests
Fit to window
Zoom out
Zoom in

Annotations

9 errors, 6 warnings, and 1 notice
tests/notebook.spec.ts:67:7 › Notebook API Visual Regression › Light theme: Cell outputs should be correct: ui-tests/tests/notebook.spec.ts#L45
1) tests/notebook.spec.ts:67:7 › Notebook API Visual Regression › Light theme: Cell outputs should be correct Error: Screenshot comparison failed: Expected an image 656px by 601px, received 656px by 414px. 22323 pixels (ratio 0.06 of all image pixels) are different. Expected: /home/runner/work/jupytercad/jupytercad/ui-tests/tests/notebook.spec.ts-snapshots/light-Notebook-ipynb-cell-3-linux.png Received: /home/runner/work/jupytercad/jupytercad/ui-tests/test-results/tests-notebook-Notebook-API-Visual-Regression-Light-theme-Cell-outputs-should-be-correct/light-Notebook-ipynb-cell-3-actual.png Diff: /home/runner/work/jupytercad/jupytercad/ui-tests/test-results/tests-notebook-Notebook-API-Visual-Regression-Light-theme-Cell-outputs-should-be-correct/light-Notebook-ipynb-cell-3-diff.png 43 | 44 | for (let c = 0; c < numCellImages; ++c) { > 45 | expect(results[c]).toMatchSnapshot( | ^ 46 | getCaptureImageName(contextPrefix, notebook, c) 47 | ); 48 | } at testCellOutputs (/home/runner/work/jupytercad/jupytercad/ui-tests/tests/notebook.spec.ts:45:26) at /home/runner/work/jupytercad/jupytercad/ui-tests/tests/notebook.spec.ts:71:5
tests/notebook.spec.ts:67:7 › Notebook API Visual Regression › Light theme: Cell outputs should be correct: ui-tests/tests/notebook.spec.ts#L45
1) tests/notebook.spec.ts:67:7 › Notebook API Visual Regression › Light theme: Cell outputs should be correct Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: Expected an image 656px by 601px, received 656px by 414px. 22323 pixels (ratio 0.06 of all image pixels) are different. Expected: /home/runner/work/jupytercad/jupytercad/ui-tests/tests/notebook.spec.ts-snapshots/light-Notebook-ipynb-cell-3-linux.png Received: /home/runner/work/jupytercad/jupytercad/ui-tests/test-results/tests-notebook-Notebook-API-Visual-Regression-Light-theme-Cell-outputs-should-be-correct-retry1/light-Notebook-ipynb-cell-3-actual.png Diff: /home/runner/work/jupytercad/jupytercad/ui-tests/test-results/tests-notebook-Notebook-API-Visual-Regression-Light-theme-Cell-outputs-should-be-correct-retry1/light-Notebook-ipynb-cell-3-diff.png 43 | 44 | for (let c = 0; c < numCellImages; ++c) { > 45 | expect(results[c]).toMatchSnapshot( | ^ 46 | getCaptureImageName(contextPrefix, notebook, c) 47 | ); 48 | } at testCellOutputs (/home/runner/work/jupytercad/jupytercad/ui-tests/tests/notebook.spec.ts:45:26) at /home/runner/work/jupytercad/jupytercad/ui-tests/tests/notebook.spec.ts:71:5
tests/notebook.spec.ts:74:7 › Notebook API Visual Regression › Dark theme: Cell outputs should be correct: ui-tests/tests/notebook.spec.ts#L45
2) tests/notebook.spec.ts:74:7 › Notebook API Visual Regression › Dark theme: Cell outputs should be correct Error: Screenshot comparison failed: Expected an image 656px by 601px, received 656px by 414px. 144518 pixels (ratio 0.37 of all image pixels) are different. Expected: /home/runner/work/jupytercad/jupytercad/ui-tests/tests/notebook.spec.ts-snapshots/dark-Notebook-ipynb-cell-3-linux.png Received: /home/runner/work/jupytercad/jupytercad/ui-tests/test-results/tests-notebook-Notebook-API-Visual-Regression-Dark-theme-Cell-outputs-should-be-correct/dark-Notebook-ipynb-cell-3-actual.png Diff: /home/runner/work/jupytercad/jupytercad/ui-tests/test-results/tests-notebook-Notebook-API-Visual-Regression-Dark-theme-Cell-outputs-should-be-correct/dark-Notebook-ipynb-cell-3-diff.png 43 | 44 | for (let c = 0; c < numCellImages; ++c) { > 45 | expect(results[c]).toMatchSnapshot( | ^ 46 | getCaptureImageName(contextPrefix, notebook, c) 47 | ); 48 | } at testCellOutputs (/home/runner/work/jupytercad/jupytercad/ui-tests/tests/notebook.spec.ts:45:26) at /home/runner/work/jupytercad/jupytercad/ui-tests/tests/notebook.spec.ts:78:5
tests/notebook.spec.ts:74:7 › Notebook API Visual Regression › Dark theme: Cell outputs should be correct: ui-tests/tests/notebook.spec.ts#L45
2) tests/notebook.spec.ts:74:7 › Notebook API Visual Regression › Dark theme: Cell outputs should be correct Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: Expected an image 656px by 601px, received 656px by 414px. 144518 pixels (ratio 0.37 of all image pixels) are different. Expected: /home/runner/work/jupytercad/jupytercad/ui-tests/tests/notebook.spec.ts-snapshots/dark-Notebook-ipynb-cell-3-linux.png Received: /home/runner/work/jupytercad/jupytercad/ui-tests/test-results/tests-notebook-Notebook-API-Visual-Regression-Dark-theme-Cell-outputs-should-be-correct-retry1/dark-Notebook-ipynb-cell-3-actual.png Diff: /home/runner/work/jupytercad/jupytercad/ui-tests/test-results/tests-notebook-Notebook-API-Visual-Regression-Dark-theme-Cell-outputs-should-be-correct-retry1/dark-Notebook-ipynb-cell-3-diff.png 43 | 44 | for (let c = 0; c < numCellImages; ++c) { > 45 | expect(results[c]).toMatchSnapshot( | ^ 46 | getCaptureImageName(contextPrefix, notebook, c) 47 | ); 48 | } at testCellOutputs (/home/runner/work/jupytercad/jupytercad/ui-tests/tests/notebook.spec.ts:45:26) at /home/runner/work/jupytercad/jupytercad/ui-tests/tests/notebook.spec.ts:78:5
tests/ui.spec.ts:51:11 › UI Test › File rendering test › Should be able to render 3M_CONNECTOR.STEP without error: ui-tests/tests/ui.spec.ts#L1
3) tests/ui.spec.ts:51:11 › UI Test › File rendering test › Should be able to render 3M_CONNECTOR.STEP without error Test timeout of 60000ms exceeded.
tests/ui.spec.ts:51:11 › UI Test › File rendering test › Should be able to render 3M_CONNECTOR.STEP without error: ui-tests/tests/ui.spec.ts#L63
3) tests/ui.spec.ts:51:11 › UI Test › File rendering test › Should be able to render 3M_CONNECTOR.STEP without error Error: locator.click: Target closed =========================== logs =========================== 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-s…>…</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" ar…>…</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" ar…>…</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" ar…>…</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" ar…>…</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" ar…>…</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" ar…>…</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" ar…>…</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" ar…>…</dialog> intercepts pointer events retrying click action, attempt #8 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" ar…>…</dialog> intercepts pointer events retrying click action, attempt #9 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" ar…>…</dialog> intercepts pointer events retrying click action, attempt #10 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" ar…>…</dialog> intercepts pointer events retrying click action, attempt #11 waiting 500ms waiting for element to be visible, enabled and stable element is visible, enabled and stable scrolling into
tests/ui.spec.ts:51:11 › UI Test › File rendering test › Should be able to render 3M_CONNECTOR.STEP without error: ui-tests/tests/ui.spec.ts#L1
3) tests/ui.spec.ts:51:11 › UI Test › File rendering test › Should be able to render 3M_CONNECTOR.STEP without error Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Test timeout of 60000ms exceeded.
tests/ui.spec.ts:51:11 › UI Test › File rendering test › Should be able to render 3M_CONNECTOR.STEP without error: ui-tests/tests/ui.spec.ts#L63
3) tests/ui.spec.ts:51:11 › UI Test › File rendering test › Should be able to render 3M_CONNECTOR.STEP without error Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: locator.click: Target closed =========================== logs =========================== 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-s…>…</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" ar…>…</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" ar…>…</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" ar…>…</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" ar…>…</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" ar…>…</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" ar…>…</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" ar…>…</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" ar…>…</dialog> intercepts pointer events retrying click action, attempt #8 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" ar…>…</dialog> intercepts pointer events retrying click action, attempt #9 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" ar…>…</dialog> intercepts pointer events retrying click action, attempt #10 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" ar…>…</dialog> intercepts pointer events retrying click action, attempt #11 waiting 500ms waiting for elemen
Integration tests
Process completed with exit code 1.
Check Links
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-python@v4, actions/cache@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build jupytercad
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/cache@v2, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build jupytercad
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/
Build jupytercad
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/
test_isolated
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/setup-python@v4, actions/download-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Integration tests
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/download-artifact@v3, actions/cache@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
🎭 Playwright Run Summary
3 failed tests/notebook.spec.ts:67:7 › Notebook API Visual Regression › Light theme: Cell outputs should be correct tests/notebook.spec.ts:74:7 › Notebook API Visual Regression › Dark theme: Cell outputs should be correct tests/ui.spec.ts:51:11 › UI Test › File rendering test › Should be able to render 3M_CONNECTOR.STEP without error 9 passed (3.4m)

Artifacts

Produced during runtime
Name Size
extension-artifacts Expired
22.9 MB
jupytercad-playwright-tests Expired
8.04 MB