test(ui): Fix failing Jupyter test on Windows #14840
test.yaml
on: pull_request
Setup workflow
5s
Pixi lock
11s
Matrix: core_test_suite
Matrix: type_test_suite
Matrix: ui_test_suite
Matrix: unit_test_suite
result:test
26s
Annotations
6 errors and 3 warnings
|
ui:test-ui:windows-latest
Process completed with exit code 1.
|
|
ui:test-ui:windows-latest:
panel\tests\ui\layout\test_card.py#L207
test_card_widget_not_collapsed[chromium]
AssertionError: assert not True
+ where True = Card(collapsed=True, header=Row, title='MyTitle')\n [0] Markdown(str).collapsed
|
|
ui:test-ui:windows-latest:
panel\tests\ui\layout\test_card.py#L207
test_card_widget_not_collapsed[chromium]
AssertionError: assert not True
+ where True = Card(collapsed=True, header=Row, title='MyTitle')\n [0] Markdown(str).collapsed
|
|
ui:test-ui:windows-latest:
panel\tests\ui\io\test_jupyterlite.py#L65
test_jupyterlite_execution[chromium]
AssertionError: Locator expected to have attribute 'idle'
Actual value: unknown
Call log:
- Expect "to_have_attribute" with timeout 60000ms
- waiting for locator(".jp-Notebook-ExecutionIndicator")
5 � locator resolved to <div title="" data-status="initializing" class="jp-Notebook-ExecutionIndicator">�</div>
- unexpected value "initializing"
57 � locator resolved to <div title="" data-status="unknown" class="jp-Notebook-ExecutionIndicator">�</div>
- unexpected value "unknown"
|
|
ui:test-ui:windows-latest:
panel\tests\ui\io\test_jupyterlite.py#L65
test_jupyterlite_execution[chromium]
AssertionError: Locator expected to have attribute 'idle'
Actual value: unknown
Call log:
- Expect "to_have_attribute" with timeout 60000ms
- waiting for locator(".jp-Notebook-ExecutionIndicator")
5 × locator resolved to <div title="" data-status="initializing" class="jp-Notebook-ExecutionIndicator">…</div>
- unexpected value "initializing"
57 × locator resolved to <div title="" data-status="unknown" class="jp-Notebook-ExecutionIndicator">…</div>
- unexpected value "unknown"
|
|
result:test
Process completed with exit code 1.
|
|
ui:test-ui:macos-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ifaxity/wait-on-action@v1.2.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ui:test-ui:ubuntu-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ifaxity/wait-on-action@v1.2.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ui:test-ui:windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ifaxity/wait-on-action@v1.2.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
pixi-lock
|
462 KB |
sha256:95c5476963a59f9a4f57026a01f25cf409fc0fe62111dc8e4bfe11d44b5c035b
|
|
|
ui_screenshots_Windows
|
28.7 MB |
sha256:feb87435b3777bc463b01cdd791379c798cea923a58707abc661419d86e6eb5b
|
|
|
ui_screenshots_macOS
|
316 KB |
sha256:3533b242aee00eab2852c7dfbae4234d7e878f603f1829db2d19b5659345533c
|
|