1) tests/sketcher.spec.ts:56:7 › Sketcher test › Should draw a circle ──────────────────────────── Error: Screenshot comparison failed: 12243 pixels (ratio 0.02 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/sketcher.spec.ts-snapshots/Sketcher-Circle-test-jcad-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-sketcher-Sketcher-test-Should-draw-a-circle/Sketcher-Circle-test-jcad-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-sketcher-Sketcher-test-Should-draw-a-circle/Sketcher-Circle-test-jcad-diff.png 92 | const dialog = await page.$('.lm-Widget.lm-Panel.jp-Dialog-content'); 93 | if (dialog) { > 94 | expect(await dialog.screenshot()).toMatchSnapshot({ | ^ 95 | name: `Sketcher-Circle-${fileName}.png`, 96 | maxDiffPixelRatio: 0.01 97 | }); at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/sketcher.spec.ts:94:41

1) tests/sketcher.spec.ts:56:7 › Sketcher test › Should draw a circle ──────────────────────────── Retry #1 ─────────────────────────────────────────────────────────────────────────────────────── Error: Screenshot comparison failed: 12243 pixels (ratio 0.02 of all image pixels) are different. Expected: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/sketcher.spec.ts-snapshots/Sketcher-Circle-test-jcad-linux.png Received: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-sketcher-Sketcher-test-Should-draw-a-circle-retry1/Sketcher-Circle-test-jcad-actual.png Diff: /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/test-results/tests-sketcher-Sketcher-test-Should-draw-a-circle-retry1/Sketcher-Circle-test-jcad-diff.png 92 | const dialog = await page.$('.lm-Widget.lm-Panel.jp-Dialog-content'); 93 | if (dialog) { > 94 | expect(await dialog.screenshot()).toMatchSnapshot({ | ^ 95 | name: `Sketcher-Circle-${fileName}.png`, 96 | maxDiffPixelRatio: 0.01 97 | }); at /home/runner/work/JupyterCAD/JupyterCAD/ui-tests/tests/sketcher.spec.ts:94:41

2) tests/ui.spec.ts:357:9 › UI Test › Console activation test › should open console ────────────── Error: Screenshot comparison failed: 12887 pixels (ratio 0.04 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: 12884 pixels (ratio 0.04 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/