Merge pull request #61 from ric-v/main #19
ric-vtest.yml
on: push
Matrix: integration-tests
Matrix: unit-tests
renderer-component-tests
51s
docker-integration
6h 5m
lint-and-format
34s
security-audit
8s
coverage-report
7s
Annotations
31 errors and 8 warnings
|
renderer-component-tests
Process completed with exit code 1.
|
|
unit-tests (18.x):
src/SavedQueryDetailsPanel.ts#L79
Property 'dispose' does not exist on type 'WebviewPanel'.
|
|
unit-tests (18.x):
src/SavedQueryDetailsPanel.ts#L64
Expected 1 arguments, but got 3.
|
|
unit-tests (18.x):
src/SavedQueryDetailsPanel.ts#L51
Expected 1 arguments, but got 3.
|
|
unit-tests (18.x):
src/SaveQueryPanel.ts#L328
Property 'title' does not exist on type 'WebviewPanel'.
|
|
unit-tests (18.x):
src/SaveQueryPanel.ts#L317
Property 'dispose' does not exist on type 'WebviewPanel'.
|
|
unit-tests (18.x):
src/SaveQueryPanel.ts#L162
Untyped function calls may not accept type arguments.
|
|
unit-tests (18.x):
src/SaveQueryPanel.ts#L141
Property 'dispose' does not exist on type 'WebviewPanel'.
|
|
unit-tests (18.x):
src/SaveQueryPanel.ts#L132
Expected 1 arguments, but got 3.
|
|
unit-tests (18.x):
src/SaveQueryPanel.ts#L125
Property 'dispose' does not exist on type 'WebviewPanel'.
|
|
unit-tests (18.x):
src/SaveQueryPanel.ts#L115
Expected 1 arguments, but got 3.
|
|
unit-tests (20.x)
The strategy configuration was canceled because "unit-tests._18_x" failed
|
|
unit-tests (20.x)
The operation was canceled.
|
|
unit-tests (22.x)
The strategy configuration was canceled because "unit-tests._18_x" failed
|
|
unit-tests (22.x):
src/SavedQueryDetailsPanel.ts#L79
Property 'dispose' does not exist on type 'WebviewPanel'.
|
|
unit-tests (22.x):
src/SavedQueryDetailsPanel.ts#L64
Expected 1 arguments, but got 3.
|
|
unit-tests (22.x):
src/SavedQueryDetailsPanel.ts#L51
Expected 1 arguments, but got 3.
|
|
unit-tests (22.x):
src/SaveQueryPanel.ts#L328
Property 'title' does not exist on type 'WebviewPanel'.
|
|
unit-tests (22.x):
src/SaveQueryPanel.ts#L317
Property 'dispose' does not exist on type 'WebviewPanel'.
|
|
unit-tests (22.x):
src/SaveQueryPanel.ts#L162
Untyped function calls may not accept type arguments.
|
|
unit-tests (22.x):
src/SaveQueryPanel.ts#L141
Property 'dispose' does not exist on type 'WebviewPanel'.
|
|
unit-tests (22.x):
src/SaveQueryPanel.ts#L132
Expected 1 arguments, but got 3.
|
|
unit-tests (22.x):
src/SaveQueryPanel.ts#L125
Property 'dispose' does not exist on type 'WebviewPanel'.
|
|
unit-tests (22.x):
src/SaveQueryPanel.ts#L115
Expected 1 arguments, but got 3.
|
|
integration-tests (17)
The job has exceeded the maximum execution time of 6h0m0s
|
|
integration-tests (17)
The operation was canceled.
|
|
integration-tests (12)
The job has exceeded the maximum execution time of 6h0m0s
|
|
docker-integration
The job has exceeded the maximum execution time of 6h0m0s
|
|
integration-tests (15)
The job has exceeded the maximum execution time of 6h0m0s
|
|
integration-tests (16)
The job has exceeded the maximum execution time of 6h0m0s
|
|
integration-tests (14)
The job has exceeded the maximum execution time of 6h0m0s
|
|
security-audit
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 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-and-format
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 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/
|
|
renderer-component-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/setup-node@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/
|
|
unit-tests (18.x)
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 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/
|
|
unit-tests (20.x)
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 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/
|
|
unit-tests (22.x)
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 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/
|
|
integration-tests (17)
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 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/
|
|
coverage-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. 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/
|