Chore: Fix tests and adapt parser methods for tokens size #3501
themisvaltinospr.yaml
on: pull_request
changes
6s
test-vscode
1m 1s
test-vscode-e2e
0s
Matrix: test-dbt-versions
Matrix: engine-tests-docker
doc-tests
32s
cicd-tests-windows
7m 4s
migration-test
51s
ui-style
0s
ui-test
0s
Matrix: style-and-cicd-tests
Matrix: engine-tests-cloud
Annotations
15 errors and 15 warnings
|
migration-test
Process completed with exit code 1.
|
|
engine-tests-docker (mysql)
Process completed with exit code 2.
|
|
engine-tests-docker (duckdb)
Process completed with exit code 2.
|
|
engine-tests-docker (postgres)
Process completed with exit code 2.
|
|
engine-tests-docker (risingwave)
Process completed with exit code 2.
|
|
engine-tests-docker (clickhouse)
Process completed with exit code 2.
|
|
engine-tests-docker (spark)
Process completed with exit code 2.
|
|
engine-tests-docker (mssql)
Process completed with exit code 2.
|
|
cicd-tests-windows
Process completed with exit code 1.
|
|
engine-tests-docker (trino)
Process completed with exit code 2.
|
|
style-and-cicd-tests (3.13)
Process completed with exit code 2.
|
|
style-and-cicd-tests (3.9)
Process completed with exit code 2.
|
|
style-and-cicd-tests (3.11)
Process completed with exit code 2.
|
|
style-and-cicd-tests (3.10)
Process completed with exit code 2.
|
|
style-and-cicd-tests (3.12)
Process completed with exit code 2.
|
|
changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/
|
|
engine-tests-docker (mysql)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
engine-tests-docker (duckdb)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
engine-tests-docker (postgres)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
engine-tests-docker (risingwave)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
engine-tests-docker (clickhouse)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
engine-tests-docker (spark)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
engine-tests-docker (mssql)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
cicd-tests-windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
engine-tests-docker (trino)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
style-and-cicd-tests (3.13)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
style-and-cicd-tests (3.9)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
style-and-cicd-tests (3.11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
style-and-cicd-tests (3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
|
style-and-cicd-tests (3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
test-results-docker-clickhouse
|
10.5 KB |
sha256:53cccf67fcafbf493cb1646e7b1e016e0c34819ca8d990221178d9e9d0861097
|
|
|
test-results-docker-duckdb
|
8.07 KB |
sha256:aa0a7b42c57cb564404f72f54eef4f59ac8dfd246068593aa2099b04ddf5fea8
|
|
|
test-results-docker-mssql
|
8.35 KB |
sha256:42026e046a89ce03034d6a9e093f879cf186a879978e5f2ee63d5c2e87c87964
|
|
|
test-results-docker-mysql
|
9.59 KB |
sha256:fb7c3b036fd2f80877630c86f3ec704cff7583d0d717194d8a3c85ec3a2a80d9
|
|
|
test-results-docker-postgres
|
10.4 KB |
sha256:5568ae70e93062929526bbc2e1c38ffb08963e1b671b585dc71e09e5d2d316aa
|
|
|
test-results-docker-risingwave
|
7.95 KB |
sha256:0660e6153a65b5ff377e4f57be982e10494af1c96abe2675c67a3e1d99948fe6
|
|
|
test-results-docker-spark
|
12.4 KB |
sha256:7094e798624e8dd7a69ff0f9fc5f71a3a41fbe81ec8a160720276bec3450f5ee
|
|
|
test-results-docker-trino
|
14.2 KB |
sha256:5774910db154b92d94779c9e07326966e206dd1a039951ab545ec94ef5b464cb
|
|
|
test-results-style-cicd-3.10
|
312 KB |
sha256:84608d1d596729082ef9006fd0b02de3c2b34a7ee5dcda88998dfa9c60a188e1
|
|
|
test-results-style-cicd-3.11
|
343 KB |
sha256:dc6df8911688da7277fd71626ca5253f5c933c9ab83f7d4455fabae5e53a6f8e
|
|
|
test-results-style-cicd-3.12
|
339 KB |
sha256:3a1a97f740fdad16d1c2633a0aecc71bb4bc25636683929b53ecbc073d0e0d77
|
|
|
test-results-style-cicd-3.13
|
340 KB |
sha256:bc3402276bb86e29faffddfb5621f0bd328e96fbc03288b43e422f5e54bc0a7b
|
|
|
test-results-style-cicd-3.9
|
311 KB |
sha256:c3311e7f3d209a8570557f9a5590d3962bf8f32d18a9f7392c20bb047f34e334
|
|
|
test-results-windows
|
189 KB |
sha256:afdc8baf3a7285f7c08738f72711797b10b3907ee765a7014f369662d5c8c698
|
|