migrate circleci to github workflow #978
T4rk1ntesting.yml
on: pull_request
Build Dash Package
2m 54s
Detect Relevant Path Changes
5s
Build on Windows
4m 47s
Matrix: test-main
Matrix: lint-unit
Matrix: dcc-test
Matrix: html-test
Matrix: background-callbacks
Matrix: table-server
Dash Table Visual Tests
3m 17s
Matrix: dcc-lint
Matrix: table-unit
Consolidated Test Report
8s
Store Build Artifacts
0s
Annotations
22 errors and 51 warnings
|
Main Dash Tests (Python 3.8, Group 3)
Process completed with exit code 1.
|
|
Main Dash Tests (Python 3.8, Group 2)
Process completed with exit code 1.
|
|
Main Dash Tests (Python 3.8, Group 1)
Process completed with exit code 1.
|
|
Main Dash Tests (Python 3.12, Group 1)
Process completed with exit code 1.
|
|
Main Dash Tests (Python 3.12, Group 3)
Process completed with exit code 1.
|
|
Main Dash Tests (Python 3.12, Group 2)
Process completed with exit code 1.
|
|
DCC Integration Tests (Python 3.8, Group 2)
Process completed with exit code 1.
|
|
DCC Integration Tests (Python 3.12, Group 2)
Process completed with exit code 1.
|
|
DCC Integration Tests (Python 3.12, Group 1)
Process completed with exit code 1.
|
|
DCC Integration Tests (Python 3.8, Group 1)
Process completed with exit code 1.
|
|
pytest ► components.dash-core-components.tests.integration.calendar.test_a11y_date_picker_single ► test_a11y007_all_keyboard_keys_respect_min_max:
test-results/dcc-test-results-py3.12-group1/junit_intg.xml#L0
Failed test found in:
test-results/dcc-test-results-py3.12-group1/junit_intg.xml
Error:
dash_dcc = <conftest._ReusableDashCoreComponentsComposite object at 0x7faf453f75c0>
|
|
pytest ► components.dash-core-components.tests.integration.dropdown.test_dynamic_options ► test_dddo001_dynamic_options:
test-results/dcc-test-results-py3.12-group1/junit_intg.xml#L0
Failed test found in:
test-results/dcc-test-results-py3.12-group1/junit_intg.xml
Error:
dash_dcc = <conftest._ReusableDashCoreComponentsComposite object at 0x7faf45c93200>
|
|
pytest ► components.dash-core-components.tests.integration.link.test_link_children ► test_lich002_children:
test-results/dcc-test-results-py3.12-group2/junit_intg.xml#L0
Failed test found in:
test-results/dcc-test-results-py3.12-group2/junit_intg.xml
Error:
dash_dcc = <conftest._ReusableDashCoreComponentsComposite object at 0x7f73c6ae06e0>
|
|
pytest ► components.dash-core-components.tests.integration.misc.test_persistence ► test_msps001_basic_persistence:
test-results/dcc-test-results-py3.12-group2/junit_intg.xml#L0
Failed test found in:
test-results/dcc-test-results-py3.12-group2/junit_intg.xml
Error:
self = <conftest.DashCoreComponentsComposite object at 0x7f73c6599d30>
|
|
pytest ► components.dash-core-components.tests.integration.sliders.test_sliders ► test_slsl003_out_of_range_marks_slider:
test-results/dcc-test-results-py3.12-group2/junit_intg.xml#L0
Failed test found in:
test-results/dcc-test-results-py3.12-group2/junit_intg.xml
Error:
dash_dcc = <conftest._ReusableDashCoreComponentsComposite object at 0x7f73c6713b30>
|
|
pytest ► components.dash-core-components.tests.integration.calendar.test_a11y_date_picker_single ► test_a11y007_all_keyboard_keys_respect_min_max:
test-results/dcc-test-results-py3.8-group1/junit_intg.xml#L0
Failed test found in:
test-results/dcc-test-results-py3.8-group1/junit_intg.xml
Error:
dash_dcc = <conftest._ReusableDashCoreComponentsComposite object at 0x7f684a0976a0>
|
|
pytest ► components.dash-core-components.tests.integration.dropdown.test_dynamic_options ► test_dddo001_dynamic_options:
test-results/dcc-test-results-py3.8-group1/junit_intg.xml#L0
Failed test found in:
test-results/dcc-test-results-py3.8-group1/junit_intg.xml
Error:
dash_dcc = <conftest._ReusableDashCoreComponentsComposite object at 0x7f6848312850>
|
|
pytest ► components.dash-core-components.tests.integration.sliders.test_sliders ► test_slsl003_out_of_range_marks_slider:
test-results/dcc-test-results-py3.8-group2/junit_intg.xml#L0
Failed test found in:
test-results/dcc-test-results-py3.8-group2/junit_intg.xml
Error:
dash_dcc = <conftest._ReusableDashCoreComponentsComposite object at 0x7fd0ac89eca0>
|
|
pytest ► tests.integration.callbacks.test_basic_callback ► test_cbsc004_callback_using_unloaded_async_component:
test-results/test-main-results-py3.12-group1/junit_intg.xml#L0
Failed test found in:
test-results/test-main-results-py3.12-group1/junit_intg.xml
Error:
dash_duo = <dash.testing.plugin._ReusableDashComposite object at 0x7ffb20a169c0>
|
|
pytest ► tests.integration.callbacks.test_callback_optional ► test_cbop002_optional_state:
test-results/test-main-results-py3.12-group1/junit_intg.xml#L0
Failed test found in:
test-results/test-main-results-py3.12-group1/junit_intg.xml
Error:
dash_duo = <dash.testing.plugin._ReusableDashComposite object at 0x7ffb21a1e6f0>
|
|
pytest ► tests.integration.renderer.test_component_as_prop ► test_rdcap001_component_as_prop:
test-results/test-main-results-py3.12-group2/junit_intg.xml#L0
Failed test found in:
test-results/test-main-results-py3.12-group2/junit_intg.xml
Error:
dash_duo = <dash.testing.plugin._ReusableDashComposite object at 0x7f89cb024ce0>
|
|
Consolidated Test Report
Process completed with exit code 1.
|
|
Detect Relevant Path Changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, dorny/paths-filter@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build Dash Package
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
DCC Lint Tests (Python 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
DCC Lint Tests (Python 3.12):
components/dash-core-components/src/utils/calendar/Calendar.tsx#L26
'isSameDay' is defined but never used
|
|
DCC Lint Tests (Python 3.12):
components/dash-core-components/src/types.ts#L1
'DetailedHTMLProps' is defined but never used
|
|
DCC Lint Tests (Python 3.12):
components/dash-core-components/src/types.ts#L1
'ButtonHTMLAttributes' is defined but never used
|
|
DCC Lint Tests (Python 3.12):
components/dash-core-components/src/fragments/RangeSlider.tsx#L41
'count' is assigned a value but never used
|
|
DCC Lint Tests (Python 3.12):
components/dash-core-components/src/fragments/RangeSlider.tsx#L39
'allowCross' is assigned a value but never used
|
|
DCC Lint Tests (Python 3.12):
components/dash-core-components/src/fragments/DatePickerSingle.tsx#L67
Unexpected any. Specify a different type
|
|
DCC Lint Tests (Python 3.12):
components/dash-core-components/src/fragments/DatePickerRange.tsx#L109
Unexpected any. Specify a different type
|
|
DCC Lint Tests (Python 3.12):
components/dash-core-components/src/fragments/DatePickerRange.tsx#L108
Unexpected any. Specify a different type
|
|
DCC Lint Tests (Python 3.12):
components/dash-core-components/src/components/Textarea.tsx#L38
'n_clicks_timestamp' is assigned a value but never used
|
|
DCC Lint Tests (Python 3.12):
components/dash-core-components/src/components/Textarea.tsx#L36
'n_blur_timestamp' is assigned a value but never used
|
|
DCC Lint Tests (Python 3.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
DCC Lint Tests (Python 3.8):
components/dash-core-components/src/utils/calendar/Calendar.tsx#L26
'isSameDay' is defined but never used
|
|
DCC Lint Tests (Python 3.8):
components/dash-core-components/src/types.ts#L1
'DetailedHTMLProps' is defined but never used
|
|
DCC Lint Tests (Python 3.8):
components/dash-core-components/src/types.ts#L1
'ButtonHTMLAttributes' is defined but never used
|
|
DCC Lint Tests (Python 3.8):
components/dash-core-components/src/fragments/RangeSlider.tsx#L41
'count' is assigned a value but never used
|
|
DCC Lint Tests (Python 3.8):
components/dash-core-components/src/fragments/RangeSlider.tsx#L39
'allowCross' is assigned a value but never used
|
|
DCC Lint Tests (Python 3.8):
components/dash-core-components/src/fragments/DatePickerSingle.tsx#L67
Unexpected any. Specify a different type
|
|
DCC Lint Tests (Python 3.8):
components/dash-core-components/src/fragments/DatePickerRange.tsx#L109
Unexpected any. Specify a different type
|
|
DCC Lint Tests (Python 3.8):
components/dash-core-components/src/fragments/DatePickerRange.tsx#L108
Unexpected any. Specify a different type
|
|
DCC Lint Tests (Python 3.8):
components/dash-core-components/src/components/Textarea.tsx#L38
'n_clicks_timestamp' is assigned a value but never used
|
|
DCC Lint Tests (Python 3.8):
components/dash-core-components/src/components/Textarea.tsx#L36
'n_blur_timestamp' is assigned a value but never used
|
|
Table Unit/Lint Tests (Python 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build on Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
HTML Components Tests (Python 3.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
HTML Components Tests (Python 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Lint & Unit Tests (Python 3.8)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Lint & Unit Tests (Python 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Typing Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
DCC Integration Tests (Python 3.8, Group 3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
DCC Integration Tests (Python 3.12, Group 3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Dash Table Visual Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Main Dash Tests (Python 3.8, Group 3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Main Dash Tests (Python 3.8, Group 2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Main Dash Tests (Python 3.8, Group 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Main Dash Tests (Python 3.12, Group 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Main Dash Tests (Python 3.12, Group 3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Main Dash Tests (Python 3.12, Group 2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Table Server Tests (Group 3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Table Server Tests (Group 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Table Server Tests (Group 2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
DCC Integration Tests (Python 3.8, Group 2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
DCC Integration Tests (Python 3.12, Group 2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Run Background & Async Callback Tests (Python 3.9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
DCC Integration Tests (Python 3.12, Group 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
DCC Integration Tests (Python 3.8, Group 1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Run Background & Async Callback Tests (Python 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-node@v4, actions/setup-python@v5, actions/upload-artifact@v4, browser-actions/setup-chrome@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Consolidated Test Report
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, dorny/test-reporter@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Consolidated Test Report
Test report summary exceeded limit of 65535 bytes and will be trimmed
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
background-test-results-py3.12
Expired
|
2 KB |
sha256:6582b98108852f2fe91b013f2025ad4cdb4f8cf7b6b0f82653f06065e3d6c4a4
|
|
|
background-test-results-py3.9
Expired
|
2 KB |
sha256:d0c181bfa5a45d5d88481134652c53402bbae3601df0acbbdb1559c0f92dd39a
|
|
|
dash-components
Expired
|
4.64 MB |
sha256:a9da2fe9f5ee232f579e4b8b6042f697bf20e386d16e0b5b22b4579829993450
|
|
|
dash-packages
Expired
|
6.84 MB |
sha256:675b31cde10024c546ba9558e602f6db2bf0280cc4a350bad15c4a87040872c1
|
|
|
dcc-test-results-py3.12-group1
Expired
|
6.74 KB |
sha256:96399a8157c01ecb8b8b37b26ae70c0f92c27837a9723e298b2f6ff525fd94c6
|
|
|
dcc-test-results-py3.12-group2
Expired
|
6.67 KB |
sha256:fe4404a1b264c6253ba08cd01b49677eb195a264171f8d94f346625fdcefa672
|
|
|
dcc-test-results-py3.12-group3
Expired
|
1.19 KB |
sha256:03b10de7deb79e03e337145c2d58a179d71b320cb8b2b2f4c06be7c735f34e7c
|
|
|
dcc-test-results-py3.8-group1
Expired
|
6.66 KB |
sha256:8a7d6d359e18d3766a81b0d9b087abd4aec9c114cb3a6c31e9a4fb7b49751e61
|
|
|
dcc-test-results-py3.8-group2
Expired
|
3.75 KB |
sha256:fab6051931aea006043464c2f1c2a5eefb6a0f56f8728aac885110df8e382b03
|
|
|
dcc-test-results-py3.8-group3
Expired
|
1.2 KB |
sha256:b9655fdce4b80d9d626447953a0b1289aab193ac099aa2b95b6571a7292a4b22
|
|
|
html-test-results-py3.12
Expired
|
541 Bytes |
sha256:532804ccb2f6d5c28a37301b589f2ac7ccfae7cfd4cdae286095c9b5f68610b3
|
|
|
html-test-results-py3.8
Expired
|
537 Bytes |
sha256:26ff6255dcb1009d10008480369adc115c11a25daf3fcbf87dcfefcc0846ea2f
|
|
|
table-server-results-group1
Expired
|
2.27 KB |
sha256:766511a8f0ed54a4972c8235e0b7d2fe1f48fac3a048d3168359969181e966b3
|
|
|
table-server-results-group2
Expired
|
3.46 KB |
sha256:3152983469e610ddb7183f39b8b5e99009648b80c5a757133435239bae9930b2
|
|
|
table-server-results-group3
Expired
|
2.46 KB |
sha256:8380359164b2ce67703fc2ed29b693dde232e8aad72a0f007a142ba69d962ba3
|
|
|
test-main-dash-artifacts-py3.12-group1
Expired
|
7.14 KB |
sha256:15bfaf76494b54f76f0b2f3bf292b9c43f0fe15f15573627f97af3930d5dd1c3
|
|
|
test-main-dash-artifacts-py3.12-group2
Expired
|
19.8 KB |
sha256:c2a08f6e10ad8c7bb446ce299e519bf4b316d7742e1a203aa7ede792b393be66
|
|
|
test-main-dash-artifacts-py3.12-group3
Expired
|
18.5 KB |
sha256:49e6000e9f586b2d60d7f95a103b4e3f6f013a1f767061894631705e7fc7bddb
|
|
|
test-main-dash-artifacts-py3.8-group1
Expired
|
7.18 KB |
sha256:5101813eb34c483eef16e3c250233873876c629bc2371ad331aaf2f40cf60b03
|
|
|
test-main-dash-artifacts-py3.8-group2
Expired
|
20.1 KB |
sha256:26df62e7e49215d69f3483bbdad64603a3e5041a792583e06716c982d70d89b4
|
|
|
test-main-dash-artifacts-py3.8-group3
Expired
|
18.4 KB |
sha256:6c10ba0454f3dd11bd91cc01bd71678748a5234d3a6c92bb0b8c81476fd4b159
|
|
|
test-main-results-py3.12-group1
Expired
|
4.61 KB |
sha256:54d33d9f8a0813580a2784960eab1359faf71796ee35cba1eebeb1827d146118
|
|
|
test-main-results-py3.12-group2
Expired
|
4.8 KB |
sha256:daf8846999eb5774fca83a8369958fee415608c67c5aa8636b9f9354509e5309
|
|
|
test-main-results-py3.12-group3
Expired
|
7.74 KB |
sha256:d9548a55a2691181d537ba18294d3c370c1c6ed61c74bb21817bb5ab8d0b31be
|
|
|
test-main-results-py3.8-group1
Expired
|
4.58 KB |
sha256:928979956a1a96714962309152214ac2885c4bc1c52d67361c2bec7f46013d4f
|
|
|
test-main-results-py3.8-group2
Expired
|
4.78 KB |
sha256:4aa077d827ceeb7af716628f48f743dfb75b1e79538a5adad046b440f8ee8411
|
|
|
test-main-results-py3.8-group3
Expired
|
7.71 KB |
sha256:8439f2c5da031581fe01b01c93a899c3359a9744a4162c732549400b1fb7a7fd
|
|