Skip to content

Update ThreeJS

Update ThreeJS #1549

Triggered via pull request September 23, 2024 10:11
Status Failure
Total duration 11m 55s
Artifacts 5

build.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors, 8 warnings, and 1 notice
tests/notebook.spec.ts:71:7 › Notebook API Visual Regression › Light theme: Cell outputs should be correct: ui-tests/tests/notebook.spec.ts#L49
1) tests/notebook.spec.ts:71:7 › Notebook API Visual Regression › Light theme: Cell outputs should be correct Error: Screenshot comparison failed: 3119 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/notebook.spec.ts-snapshots/light-Notebook-ipynb-cell-0-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-notebook-Notebook-AP-da5b3-l-outputs-should-be-correct/light-Notebook-ipynb-cell-0-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-notebook-Notebook-AP-da5b3-l-outputs-should-be-correct/light-Notebook-ipynb-cell-0-diff.png 47 | 48 | for (let c = 0; c < numCellImages; ++c) { > 49 | expect(results[c]).toMatchSnapshot( | ^ 50 | getCaptureImageName(contextPrefix, notebook, c) 51 | ); 52 | } at testCellOutputs (/home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/notebook.spec.ts:49:26) at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/notebook.spec.ts:75:5
tests/notebook.spec.ts:71:7 › Notebook API Visual Regression › Light theme: Cell outputs should be correct: ui-tests/tests/notebook.spec.ts#L49
1) tests/notebook.spec.ts:71:7 › Notebook API Visual Regression › Light theme: Cell outputs should be correct Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 3119 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/notebook.spec.ts-snapshots/light-Notebook-ipynb-cell-0-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-notebook-Notebook-AP-da5b3-l-outputs-should-be-correct-retry1/light-Notebook-ipynb-cell-0-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-notebook-Notebook-AP-da5b3-l-outputs-should-be-correct-retry1/light-Notebook-ipynb-cell-0-diff.png 47 | 48 | for (let c = 0; c < numCellImages; ++c) { > 49 | expect(results[c]).toMatchSnapshot( | ^ 50 | getCaptureImageName(contextPrefix, notebook, c) 51 | ); 52 | } at testCellOutputs (/home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/notebook.spec.ts:49:26) at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/notebook.spec.ts:75:5
tests/notebook.spec.ts:78:7 › Notebook API Visual Regression › Dark theme: Cell outputs should be correct: ui-tests/tests/notebook.spec.ts#L49
2) tests/notebook.spec.ts:78:7 › Notebook API Visual Regression › Dark theme: Cell outputs should be correct Error: Screenshot comparison failed: 3376 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/notebook.spec.ts-snapshots/dark-Notebook-ipynb-cell-0-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-notebook-Notebook-AP-aebed-l-outputs-should-be-correct/dark-Notebook-ipynb-cell-0-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-notebook-Notebook-AP-aebed-l-outputs-should-be-correct/dark-Notebook-ipynb-cell-0-diff.png 47 | 48 | for (let c = 0; c < numCellImages; ++c) { > 49 | expect(results[c]).toMatchSnapshot( | ^ 50 | getCaptureImageName(contextPrefix, notebook, c) 51 | ); 52 | } at testCellOutputs (/home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/notebook.spec.ts:49:26) at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/notebook.spec.ts:82:5
tests/notebook.spec.ts:78:7 › Notebook API Visual Regression › Dark theme: Cell outputs should be correct: ui-tests/tests/notebook.spec.ts#L49
2) tests/notebook.spec.ts:78:7 › Notebook API Visual Regression › Dark theme: Cell outputs should be correct Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 3376 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/notebook.spec.ts-snapshots/dark-Notebook-ipynb-cell-0-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-notebook-Notebook-AP-aebed-l-outputs-should-be-correct-retry1/dark-Notebook-ipynb-cell-0-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-notebook-Notebook-AP-aebed-l-outputs-should-be-correct-retry1/dark-Notebook-ipynb-cell-0-diff.png 47 | 48 | for (let c = 0; c < numCellImages; ++c) { > 49 | expect(results[c]).toMatchSnapshot( | ^ 50 | getCaptureImageName(contextPrefix, notebook, c) 51 | ); 52 | } at testCellOutputs (/home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/notebook.spec.ts:49:26) at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/notebook.spec.ts:82:5
tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render test.jcad without error: ui-tests/tests/ui.spec.ts#L75
3) tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render test.jcad without error Error: Screenshot comparison failed: 23822 pixels (ratio 0.02 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts-snapshots/Render-test-jcad-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-File-oper-f32dc-der-test-jcad-without-error/Render-test-jcad-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-File-oper-f32dc-der-test-jcad-without-error/Render-test-jcad-diff.png 73 | expect(errors).toBe(0); 74 | if (main) { > 75 | expect(await main.screenshot()).toMatchSnapshot({ | ^ 76 | name: `Render-${file}.png`, 77 | maxDiffPixelRatio: 0.01 78 | }); at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts:75:43
tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render test.jcad without error: ui-tests/tests/ui.spec.ts#L75
3) tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render test.jcad without error Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 23822 pixels (ratio 0.02 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts-snapshots/Render-test-jcad-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-File-oper-f32dc-der-test-jcad-without-error-retry1/Render-test-jcad-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-File-oper-f32dc-der-test-jcad-without-error-retry1/Render-test-jcad-diff.png 73 | expect(errors).toBe(0); 74 | if (main) { > 75 | expect(await main.screenshot()).toMatchSnapshot({ | ^ 76 | name: `Render-${file}.png`, 77 | maxDiffPixelRatio: 0.01 78 | }); at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts:75:43
tests/ui.spec.ts:106:9 › UI Test › File operator test › Should be able to add object to scene: ui-tests/tests/ui.spec.ts#L141
4) tests/ui.spec.ts:106:9 › UI Test › File operator test › Should be able to add object to scene ─ Error: Screenshot comparison failed: 59157 pixels (ratio 0.04 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts-snapshots/Operator-Add-test-jcad-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-File-oper-70534-able-to-add-object-to-scene/Operator-Add-test-jcad-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-File-oper-70534-able-to-add-object-to-scene/Operator-Add-test-jcad-diff.png 139 | const main = await page.$('#jp-main-split-panel'); 140 | if (main) { > 141 | expect(await main.screenshot()).toMatchSnapshot({ | ^ 142 | name: `Operator-Add-${fileName}.png`, 143 | maxDiffPixelRatio: 0.01 144 | }); at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts:141:41
tests/ui.spec.ts:106:9 › UI Test › File operator test › Should be able to add object to scene: ui-tests/tests/ui.spec.ts#L141
4) tests/ui.spec.ts:106:9 › UI Test › File operator test › Should be able to add object to scene ─ Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 59153 pixels (ratio 0.04 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts-snapshots/Operator-Add-test-jcad-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-File-oper-70534-able-to-add-object-to-scene-retry1/Operator-Add-test-jcad-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-File-oper-70534-able-to-add-object-to-scene-retry1/Operator-Add-test-jcad-diff.png 139 | const main = await page.$('#jp-main-split-panel'); 140 | if (main) { > 141 | expect(await main.screenshot()).toMatchSnapshot({ | ^ 142 | name: `Operator-Add-${fileName}.png`, 143 | maxDiffPixelRatio: 0.01 144 | }); at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts:141:41
tests/ui.spec.ts:148:9 › UI Test › File operator test › Should be able to remove object: ui-tests/tests/ui.spec.ts#L183
5) tests/ui.spec.ts:148:9 › UI Test › File operator test › Should be able to remove object ─────── Error: Screenshot comparison failed: 23913 pixels (ratio 0.02 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts-snapshots/Operator-Remove-test-jcad-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-File-oper-ec544-ld-be-able-to-remove-object/Operator-Remove-test-jcad-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-File-oper-ec544-ld-be-able-to-remove-object/Operator-Remove-test-jcad-diff.png 181 | const main = await page.$('#jp-main-split-panel'); 182 | if (main) { > 183 | expect(await main.screenshot()).toMatchSnapshot({ | ^ 184 | name: `Operator-Remove-${fileName}.png`, 185 | maxDiffPixelRatio: 0.01 186 | }); at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts:183:41
tests/ui.spec.ts:148:9 › UI Test › File operator test › Should be able to remove object: ui-tests/tests/ui.spec.ts#L183
5) tests/ui.spec.ts:148:9 › UI Test › File operator test › Should be able to remove object ─────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 23913 pixels (ratio 0.02 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts-snapshots/Operator-Remove-test-jcad-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-File-oper-ec544-ld-be-able-to-remove-object-retry1/Operator-Remove-test-jcad-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-File-oper-ec544-ld-be-able-to-remove-object-retry1/Operator-Remove-test-jcad-diff.png 181 | const main = await page.$('#jp-main-split-panel'); 182 | if (main) { > 183 | expect(await main.screenshot()).toMatchSnapshot({ | ^ 184 | name: `Operator-Remove-${fileName}.png`, 185 | maxDiffPixelRatio: 0.01 186 | }); at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts:183:41
🎭 Playwright Run Summary
9 failed tests/notebook.spec.ts:71:7 › Notebook API Visual Regression › Light theme: Cell outputs should be correct tests/notebook.spec.ts:78:7 › Notebook API Visual Regression › Dark theme: Cell outputs should be correct tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render test.jcad without error tests/ui.spec.ts:106:9 › UI Test › File operator test › Should be able to add object to scene ── tests/ui.spec.ts:148:9 › UI Test › File operator test › Should be able to remove object ──────── tests/ui.spec.ts:190:9 › UI Test › File operator test › Should be able to edit object ────────── tests/ui.spec.ts:238:9 › UI Test › File operator test › Should be able to do multi selection ─── tests/ui.spec.ts:303:11 › UI Test › JCAD creation test › Extension activation test › should create a new JCAD file tests/ui.spec.ts:362:9 › UI Test › Console activation test › should open console ─────────────── 6 passed (3.6m)
Check Links
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/
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 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/
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
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/
Build JupyterLite
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/
Integration tests
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/
Deprecation notice: v1, v2, and v3 of the artifact actions
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/

Artifacts

Produced during runtime
Name Size
appsharingspace
355 Bytes
extension-artifacts
24.7 MB
galata-apss
355 Bytes
github-pages
28.6 MB
jupytercad-playwright-tests
11.3 MB