Skip to content

Experimental BQ support to run dbt models with ExecutionMode.AIRFLOW_ASYNC #3554

Experimental BQ support to run dbt models with ExecutionMode.AIRFLOW_ASYNC

Experimental BQ support to run dbt models with ExecutionMode.AIRFLOW_ASYNC #3554

Triggered via pull request October 1, 2024 19:07
@pankajkotipankajkoti
synchronize #1230
Status Failure
Total duration 20m 42s
Artifacts

test.yml

on: pull_request_target
Authorize
0s
Authorize
Matrix: Run-Unit-Tests
Matrix: Run-Integration-Tests-Expensive
Matrix: Run-Integration-Tests
Matrix: Run-Kubernetes-Tests
Matrix: Run-Integration-Tests-DBT-1-5-4
Matrix: Run-Integration-Tests-Sqlite
Matrix: Run-Performance-Tests
Code-Coverage
0s
Code-Coverage
Fit to window
Zoom out
Zoom in

Annotations

102 errors and 13 warnings
Run-Unit-Tests (3.11, 2.7)
Process completed with exit code 1.
Run-Unit-Tests (3.10, 2.7)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.10, 2.7)
The operation was canceled.
Run-Unit-Tests (3.10, 2.4)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.10, 2.4)
The operation was canceled.
Run-Unit-Tests (3.12, 2.10)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.12, 2.10)
The operation was canceled.
Run-Unit-Tests (3.10, 2.6)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.10, 2.6)
The operation was canceled.
Run-Unit-Tests (3.12, 2.9)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.12, 2.9)
The operation was canceled.
Run-Unit-Tests (3.9, 2.10)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.9, 2.10)
The operation was canceled.
Run-Unit-Tests (3.11, 2.10)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.11, 2.10)
The operation was canceled.
Run-Unit-Tests (3.8, 2.8)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.8, 2.8)
The operation was canceled.
Run-Unit-Tests (3.9, 2.4)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.9, 2.4)
The operation was canceled.
Run-Unit-Tests (3.8, 2.6)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.8, 2.6)
The operation was canceled.
Run-Unit-Tests (3.8, 2.9)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.8, 2.9)
The operation was canceled.
Run-Unit-Tests (3.8, 2.5)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.8, 2.5)
The operation was canceled.
Run-Unit-Tests (3.8, 2.10)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.8, 2.10)
The operation was canceled.
Run-Unit-Tests (3.11, 2.6)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.11, 2.6)
The operation was canceled.
Run-Unit-Tests (3.8, 2.4)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.8, 2.4)
The operation was canceled.
Run-Unit-Tests (3.10, 2.8)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.10, 2.8)
The operation was canceled.
Run-Unit-Tests (3.11, 2.9)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.11, 2.9)
The operation was canceled.
Run-Unit-Tests (3.9, 2.6)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.9, 2.6)
The operation was canceled.
Run-Unit-Tests (3.9, 2.8)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.9, 2.8)
The operation was canceled.
Run-Unit-Tests (3.10, 2.9)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.10, 2.9)
The operation was canceled.
Run-Unit-Tests (3.11, 2.8)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.11, 2.8)
The operation was canceled.
Run-Unit-Tests (3.10, 2.5)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.10, 2.5)
The operation was canceled.
Run-Unit-Tests (3.9, 2.5)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.9, 2.5)
The operation was canceled.
Run-Unit-Tests (3.9, 2.9)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.9, 2.9)
The operation was canceled.
Run-Unit-Tests (3.10, 2.10)
The job was canceled because "_3_11_2_7" failed.
Run-Unit-Tests (3.10, 2.10)
The operation was canceled.
Run-Kubernetes-Tests (3.11, 2.9)
Process completed with exit code 1.
Run-Integration-Tests (3.10, 2.7)
Process completed with exit code 2.
Run-Integration-Tests (3.11, 2.7)
Process completed with exit code 2.
Run-Integration-Tests (3.10, 2.10)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.10, 2.10)
The operation was canceled.
Run-Integration-Tests (3.8, 2.6)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.8, 2.6)
The operation was canceled.
Run-Integration-Tests (3.11, 2.8)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.11, 2.8)
The operation was canceled.
Run-Integration-Tests (3.8, 2.10)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.8, 2.10)
The operation was canceled.
Run-Integration-Tests (3.9, 2.9)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.9, 2.9)
The operation was canceled.
Run-Integration-Tests (3.9, 2.10)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.9, 2.10)
The operation was canceled.
Run-Integration-Tests (3.9, 2.6)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.9, 2.6)
The operation was canceled.
Run-Integration-Tests (3.8, 2.4)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.8, 2.4)
The operation was canceled.
Run-Integration-Tests (3.10, 2.8)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.10, 2.8)
The operation was canceled.
Run-Integration-Tests (3.9, 2.4)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.9, 2.4)
The operation was canceled.
Run-Integration-Tests (3.10, 2.5)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.10, 2.5)
The operation was canceled.
Run-Integration-Tests (3.11, 2.10)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.11, 2.10)
The operation was canceled.
Run-Integration-Tests (3.8, 2.5)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.8, 2.5)
The operation was canceled.
Run-Integration-Tests (3.11, 2.6)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.11, 2.6)
The operation was canceled.
Run-Integration-Tests (3.10, 2.6)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.10, 2.6)
The operation was canceled.
Run-Integration-Tests (3.11, 2.9)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.11, 2.9)
The operation was canceled.
Run-Integration-Tests (3.9, 2.5)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.9, 2.5)
The operation was canceled.
Run-Integration-Tests (3.9, 2.8)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.9, 2.8)
The operation was canceled.
Run-Integration-Tests (3.10, 2.4)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.10, 2.4)
The operation was canceled.
Run-Integration-Tests (3.10, 2.9)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.10, 2.9)
The operation was canceled.
Run-Integration-Tests (3.8, 2.9)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.8, 2.9)
The operation was canceled.
Run-Integration-Tests (3.8, 2.8)
The job was canceled because "_3_10_2_7" failed.
Run-Integration-Tests (3.8, 2.8)
The operation was canceled.
Run-Integration-Tests-Sqlite (3.11, 2.8)
Process completed with exit code 2.
Run-Integration-Tests-DBT-1-5-4 (3.11, 2.8)
Process completed with exit code 2.
Type-Check
Process completed with exit code 1.
Run-Integration-Tests-Expensive (3.11, 2.6)
Process completed with exit code 2.
Run-Unit-Tests (3.11, 2.7)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run-Kubernetes-Tests (3.11, 2.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: container-tools/kind-action@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Run-Kubernetes-Tests (3.11, 2.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-python@v4, container-tools/kind-action@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run-Integration-Tests (3.10, 2.7)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run-Integration-Tests (3.11, 2.7)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run-Performance-Tests (3.11, 2.8, 1)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run-Performance-Tests (3.11, 2.8, 10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run-Performance-Tests (3.11, 2.8, 50)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run-Performance-Tests (3.11, 2.8, 100)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run-Integration-Tests-Sqlite (3.11, 2.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run-Integration-Tests-DBT-1-5-4 (3.11, 2.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Type-Check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-python@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run-Integration-Tests-Expensive (3.11, 2.6)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/cache@v3, actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/