Migrate CircleCI to GitHub Actions #3451
eakmanrqpr.yaml
on: pull_request
changes
6s
test-vscode
53s
test-vscode-e2e
0s
Matrix: engine-tests-cloud
Matrix: test-dbt-versions
doc-tests
29s
cicd-tests-windows
5m 35s
migration-test
1m 26s
ui-style
37s
ui-test
1m 50s
Matrix: engine-tests-docker
Matrix: style-and-cicd-tests
Annotations
32 errors and 17 warnings
|
engine-tests-cloud (fabric)
Process completed with exit code 2.
|
|
engine-tests-cloud (fabric)
Process completed with exit code 2.
|
|
engine-tests-cloud (snowflake)
Process completed with exit code 1.
|
|
engine-tests-cloud (snowflake)
Process completed with exit code 1.
|
|
engine-tests-cloud (redshift)
Process completed with exit code 2.
|
|
engine-tests-cloud (gcp-postgres)
Process completed with exit code 2.
|
|
engine-tests-cloud (gcp-postgres)
Process completed with exit code 2.
|
|
style-and-cicd-tests (3.9)
Canceling since a higher priority waiting request for pr-5729 exists
|
|
style-and-cicd-tests (3.9)
The operation was canceled.
|
|
engine-tests-docker (spark)
Canceling since a higher priority waiting request for pr-5729 exists
|
|
engine-tests-docker (spark)
The operation was canceled.
|
|
style-and-cicd-tests (3.11)
Canceling since a higher priority waiting request for pr-5729 exists
|
|
style-and-cicd-tests (3.11)
The operation was canceled.
|
|
engine-tests-cloud (athena)
Canceling since a higher priority waiting request for pr-5729 exists
|
|
engine-tests-cloud (athena)
The operation was canceled.
|
|
style-and-cicd-tests (3.13)
Canceling since a higher priority waiting request for pr-5729 exists
|
|
style-and-cicd-tests (3.13)
The operation was canceled.
|
|
engine-tests-cloud (databricks)
Canceling since a higher priority waiting request for pr-5729 exists
|
|
engine-tests-cloud (databricks)
The operation was canceled.
|
|
engine-tests-docker (trino)
Canceling since a higher priority waiting request for pr-5729 exists
|
|
engine-tests-docker (trino)
The operation was canceled.
|
|
style-and-cicd-tests (3.12)
Canceling since a higher priority waiting request for pr-5729 exists
|
|
style-and-cicd-tests (3.12)
The operation was canceled.
|
|
style-and-cicd-tests (3.10)
Canceling since a higher priority waiting request for pr-5729 exists
|
|
style-and-cicd-tests (3.10)
The operation was canceled.
|
|
engine-tests-cloud (bigquery)
Canceling since a higher priority waiting request for pr-5729 exists
|
|
engine-tests-cloud (bigquery)
The operation was canceled.
|
|
engine-tests-cloud (clickhouse-cloud)
Canceling since a higher priority waiting request for pr-5729 exists
|
|
engine-tests-cloud (clickhouse-cloud)
The operation was canceled.
|
|
cicd-tests-windows
Canceling since a higher priority waiting request for pr-5729 exists
|
|
cicd-tests-windows
The operation was canceled.
|
|
.github/workflows/pr.yaml
Canceling since a higher priority waiting request for pr-5729 exists
|
|
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-cloud (fabric)
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 *** 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 ***, 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-cloud (fabric)
No files were found with the provided path: test-results/. No artifacts will be uploaded.
|
|
test-vscode
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@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/
|
|
engine-tests-cloud (snowflake)
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 *** 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 ***, 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-cloud (snowflake)
No files were found with the provided path: test-results/. No artifacts will be uploaded.
|
|
engine-tests-cloud (redshift)
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 *** 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 ***, 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-cloud (redshift)
No files were found with the provided path: test-results/. No artifacts will be uploaded.
|
|
engine-tests-cloud (gcp-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 *** 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 ***, 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-cloud (gcp-postgres)
No files were found with the provided path: test-results/. No artifacts will be uploaded.
|
|
ui-style
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, pnpm/action-setup@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/
|
|
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 (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/
|
|
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 (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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
test-results-docker-clickhouse
|
3.47 KB |
sha256:80c48ef1d5b4ec47d9999d048fbe749ccd0813778866fd0612e3c6d3c11e1da6
|
|
|
test-results-docker-duckdb
|
2.23 KB |
sha256:9ffc841465177d4207e15fe1127141f5617afbf69b7ddea8c92b23c8e2431135
|
|
|
test-results-docker-mssql
|
2.48 KB |
sha256:f221e1dbb4e2b729cff8bbae2d05e2afbcfc8361bfe113ef1eed5a3430ef4e73
|
|
|
test-results-docker-mysql
|
1.98 KB |
sha256:f63e3ef50673f43adda2645ffb6349c936e7fd6362b67c47ebb5a16018d6da28
|
|
|
test-results-docker-postgres
|
2.79 KB |
sha256:3ee727b903520fa79edffa9a654e70e4304e40c44fff11f2c33a4b23f5b29a61
|
|
|
test-results-docker-risingwave
|
2.08 KB |
sha256:eaba0313e736e9b0a293b550dc6ea8162d908719d4aac06487d2b23eb1638a3f
|
|