1) tests/notebook.spec.ts:78:7 › Notebook API Visual Regression › Dark theme: Cell outputs should be correct Error: Screenshot comparison failed: 927 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

1) tests/notebook.spec.ts:78:7 › Notebook API Visual Regression › Dark theme: Cell outputs should be correct Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 927 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

2) tests/ui.spec.ts:357:9 › UI Test › Console activation test › should open console ────────────── Error: Screenshot comparison failed: 696 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts-snapshots/JCAD-Console-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-Console-activation-test-should-open-console/JCAD-Console-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-Console-activation-test-should-open-console/JCAD-Console-diff.png 369 | 370 | if (main) { > 371 | expect(await main.screenshot()).toMatchSnapshot({ | ^ 372 | name: `JCAD-Console.png` 373 | }); 374 | } at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts:371:41

2) tests/ui.spec.ts:357:9 › UI Test › Console activation test › should open console ────────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 745 pixels (ratio 0.01 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts-snapshots/JCAD-Console-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-Console-activation-test-should-open-console-retry1/JCAD-Console-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-ui-UI-Test-Console-activation-test-should-open-console-retry1/JCAD-Console-diff.png 369 | 370 | if (main) { > 371 | expect(await main.screenshot()).toMatchSnapshot({ | ^ 372 | name: `JCAD-Console.png` 373 | }); 374 | } at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/ui.spec.ts:371:41

Process completed with exit code 1.

Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use the latest version of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-09-16-notice-of-upcoming-deprecations-and-changes-in-github-actions-services/

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/