Fix breaking viewHelper while changing camera #1656
build.yml
on: pull_request
Build jupytercad
4m 39s
Check Links
1m 21s
test_isolated
33s
deploy
0s
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:
Expected an image 656px by 601px, received 656px by 30px. 20334 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-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:
Expected an image 656px by 601px, received 656px by 30px. 20334 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-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:
Expected an image 656px by 601px, received 656px by 30px. 372251 pixels (ratio 0.95 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:
Expected an image 656px by 601px, received 656px by 30px. 372251 pixels (ratio 0.95 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/tree.spec.ts:28:7 › Tree UI test › Should display the object tree:
ui-tests/tests/tree.spec.ts#L56
3) tests/tree.spec.ts:28:7 › Tree UI test › Should display the object tree ───────────────────────
Error: expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
54 | .click();
55 |
> 56 | expect(errors).toBe(0);
| ^
57 | const tree = await page.getByRole('region', {
58 | name: 'Objects tree Section'
59 | });
at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/tree.spec.ts:56:20
|
tests/tree.spec.ts:28:7 › Tree UI test › Should display the object tree:
ui-tests/tests/tree.spec.ts#L56
3) tests/tree.spec.ts:28:7 › Tree UI test › Should display the object tree ───────────────────────
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
54 | .click();
55 |
> 56 | expect(errors).toBe(0);
| ^
57 | const tree = await page.getByRole('region', {
58 | name: 'Objects tree Section'
59 | });
at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/tree.spec.ts:56:20
|
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#L73
4) tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render test.jcad without error
Error: expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
71 | await page.waitForTimeout(1000);
72 | const main = await page.$('#jp-main-split-panel');
> 73 | expect(errors).toBe(0);
| ^
74 | if (main) {
75 | expect(await main.screenshot()).toMatchSnapshot({
76 | name: `Render-${file}.png`,
at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts:73:24
|
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#L73
4) tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render test.jcad without error
Retry #1 ───────────────────────────────────────────────────────────────────────────────────────
Error: expect(received).toBe(expected) // Object.is equality
Expected: 0
Received: 1
71 | await page.waitForTimeout(1000);
72 | const main = await page.$('#jp-main-split-panel');
> 73 | expect(errors).toBe(0);
| ^
74 | if (main) {
75 | expect(await main.screenshot()).toMatchSnapshot({
76 | name: `Render-${file}.png`,
at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts:73:24
|
tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render 3M_CONNECTOR.STEP without error:
ui-tests/tests/ui.spec.ts#L1
5) tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render 3M_CONNECTOR.STEP without error
Test timeout of 60000ms exceeded.
|
tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render 3M_CONNECTOR.STEP without error:
ui-tests/tests/ui.spec.ts#L66
5) tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render 3M_CONNECTOR.STEP 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 3M_CONNECTOR.STEP Unexpected token 'I', "ISO-10303-"... 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 3M_CONNECTOR.STEP Unexpected token 'I', "ISO-10303-"... 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 3M_CONNECTOR.STEP Unexpected token 'I', "ISO-10303-"... 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 3M_CONNECTOR.STEP Unexpected token 'I', "ISO-10303-"... 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 3M_CONNECTOR.STEP Unexpected token 'I', "ISO-10303-"... 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 3M_CONNECTOR.STEP Unexpected token 'I', "ISO-10303-"... 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 3M_CONNECTOR.STEP Unexpected token 'I', "ISO-10303-"... 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 3M_CONNECTOR.STEP Unexpected token 'I', "ISO-10303-"... is not valid JSON">…</dialog> intercepts pointer events
- retryi
|
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/
|
🎭 Playwright Run Summary
10 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/tree.spec.ts:28:7 › Tree UI test › Should display the object tree ────────────────────────
tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render test.jcad without error
tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render 3M_CONNECTOR.STEP without error
tests/ui.spec.ts:51:11 › UI Test › File operations › Should be able to render fan.stl 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:359:9 › UI Test › Console activation test › should open console ───────────────
5 passed (7.1m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
appsharingspace
|
353 Bytes |
|
extension-artifacts
|
24.7 MB |
|
galata-apss
|
355 Bytes |
|
github-pages
|
29 MB |
|
jupytercad-playwright-tests
|
12.7 MB |
|