Fix: Do not modify updated_ts when unpausing all snapshots with target name #3557
crerichapr.yaml
on: pull_request
changes
7s
test-vscode
1m 6s
test-vscode-e2e
0s
Matrix: test-dbt-versions
Matrix: engine-tests-docker
doc-tests
39s
cicd-tests-windows
2m 32s
migration-test
1m 42s
ui-style
0s
ui-test
0s
Matrix: style-and-cicd-tests
Matrix: engine-tests-cloud
Annotations
21 errors and 6 warnings
|
style-and-cicd-tests (3.10)
Canceling since a higher priority waiting request for pr-5766 exists
|
|
style-and-cicd-tests (3.10)
The operation was canceled.
|
|
style-and-cicd-tests (3.11)
Canceling since a higher priority waiting request for pr-5766 exists
|
|
style-and-cicd-tests (3.11)
The operation was canceled.
|
|
style-and-cicd-tests (3.13)
Canceling since a higher priority waiting request for pr-5766 exists
|
|
style-and-cicd-tests (3.13)
The operation was canceled.
|
|
engine-tests-docker (clickhouse)
Canceling since a higher priority waiting request for pr-5766 exists
|
|
engine-tests-docker (clickhouse)
The operation was canceled.
|
|
cicd-tests-windows
Canceling since a higher priority waiting request for pr-5766 exists
|
|
cicd-tests-windows
The operation was canceled.
|
|
engine-tests-docker (risingwave)
Canceling since a higher priority waiting request for pr-5766 exists
|
|
engine-tests-docker (risingwave)
The operation was canceled.
|
|
engine-tests-docker (spark)
Canceling since a higher priority waiting request for pr-5766 exists
|
|
engine-tests-docker (spark)
The operation was canceled.
|
|
engine-tests-docker (trino)
Canceling since a higher priority waiting request for pr-5766 exists
|
|
engine-tests-docker (trino)
The operation was canceled.
|
|
style-and-cicd-tests (3.12)
Canceling since a higher priority waiting request for pr-5766 exists
|
|
style-and-cicd-tests (3.12)
The operation was canceled.
|
|
style-and-cicd-tests (3.9)
Canceling since a higher priority waiting request for pr-5766 exists
|
|
style-and-cicd-tests (3.9)
The operation was canceled.
|
|
.github/workflows/pr.yaml
Canceling since a higher priority waiting request for pr-5766 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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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/
|
|
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. 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 | |
|---|---|---|---|
|
test-results-docker-duckdb
|
2.2 KB |
sha256:e931522f4f5c8fb66fac84c2a60675f669e8584141f65841a711bc310fac2e9a
|
|
|
test-results-docker-mssql
|
2.49 KB |
sha256:4fd69d4b6fc697c7a6af61fd45cb27e45cd7ad68d772d334ccf80d6a5859d6f5
|
|
|
test-results-docker-mysql
|
1.99 KB |
sha256:bb58abd0d997e2f34a8b56d7bcd1ba5b1eb914107d18980053e29eb1f1a80dcf
|
|
|
test-results-docker-postgres
|
2.83 KB |
sha256:87b88e24aa3932310370dab62b321e11833a4487902e6777772430a130cc29a9
|
|