Fix extension not showing up in the Settings Editor #174
Annotations
1 error and 1 notice
tests/timing_outcomes.spec.ts:20:7 › Timing outcomes › "Execution started at" state:
ui-tests/tests/timing_outcomes.spec.ts#L28
1) tests/timing_outcomes.spec.ts:20:7 › Timing outcomes › "Execution started at" state ───────────
Error: Screenshot comparison failed:
65 pixels (ratio 0.01 of all image pixels) are different.
Expected: /home/runner/work/jupyterlab-execute-time/jupyterlab-execute-time/ui-tests/tests/timing_outcomes.spec.ts-snapshots/execution-started-linux.png
Received: /home/runner/work/jupyterlab-execute-time/jupyterlab-execute-time/ui-tests/test-results/tests-timing_outcomes-Timing-outcomes-Execution-started-at-state/execution-started-actual.png
Diff: /home/runner/work/jupyterlab-execute-time/jupyterlab-execute-time/ui-tests/test-results/tests-timing_outcomes-Timing-outcomes-Execution-started-at-state/execution-started-diff.png
26 | const widget = await cell.waitForSelector('.execute-time');
27 | expect(await widget.textContent()).toContain('Execution started at');
> 28 | expect(await maskedScreenshot(widget)).toMatchSnapshot(
| ^
29 | 'execution-started.png'
30 | );
31 | });
at /home/runner/work/jupyterlab-execute-time/jupyterlab-execute-time/ui-tests/tests/timing_outcomes.spec.ts:28:44
|
🎭 Playwright Run Summary
1 flaky
tests/timing_outcomes.spec.ts:20:7 › Timing outcomes › "Execution started at" state ────────────
8 passed (1.5m)
|
Artifacts
Produced during runtime
Name | Size | |
---|---|---|
extension-artifacts
Expired
|
214 KB |
|
jupyterlab_execute_time-playwright-tests
Expired
|
6.33 MB |
|