Skip to content

Add astro cli project to run airflow+dagfactory #50

Add astro cli project to run airflow+dagfactory

Add astro cli project to run airflow+dagfactory #50

Triggered via pull request October 21, 2024 14:57
@pankajastropankajastro
synchronize #267
Status Failure
Total duration 3m 6s
Artifacts

cicd.yaml

on: pull_request_target
Matrix: Run-Unit-Tests
Matrix: Run-Integration-Tests
Static-Check
44s
Static-Check
Code-Coverage
0s
Code-Coverage
Build and publish Python 🐍 distributions 📦 to PyPI
0s
Build and publish Python 🐍 distributions 📦 to PyPI
Fit to window
Zoom out
Zoom in

Annotations

64 errors and 32 warnings
Run-Integration-Tests (3.11, 2.8)
Process completed with exit code 127.
Run-Integration-Tests (3.11, 2.10)
Process completed with exit code 127.
Run-Integration-Tests (3.9, 2.10)
Process completed with exit code 127.
Run-Integration-Tests (3.10, 2.10)
Process completed with exit code 127.
Run-Integration-Tests (3.11, 2.7)
Process completed with exit code 127.
Run-Integration-Tests (3.8, 2.10)
Process completed with exit code 127.
Run-Integration-Tests (3.10, 2.9)
Process completed with exit code 127.
Run-Integration-Tests (3.8, 2.9)
Process completed with exit code 127.
Run-Integration-Tests (3.10, 2.5)
Process completed with exit code 127.
Run-Integration-Tests (3.8, 2.3)
Process completed with exit code 127.
Run-Integration-Tests (3.8, 2.4)
Process completed with exit code 127.
Run-Integration-Tests (3.8, 2.6)
Process completed with exit code 127.
Run-Integration-Tests (3.10, 2.4)
Process completed with exit code 127.
Run-Integration-Tests (3.8, 2.2)
Process completed with exit code 127.
Run-Integration-Tests (3.12, 2.9)
Process completed with exit code 127.
Run-Integration-Tests (3.8, 2.7)
Process completed with exit code 127.
Run-Integration-Tests (3.10, 2.3)
Process completed with exit code 127.
Run-Integration-Tests (3.8, 2.5)
Process completed with exit code 127.
Run-Integration-Tests (3.8, 2.8)
Process completed with exit code 127.
Run-Integration-Tests (3.10, 2.6)
Process completed with exit code 127.
Run-Integration-Tests (3.9, 2.6)
Process completed with exit code 127.
Run-Integration-Tests (3.9, 2.2)
Process completed with exit code 127.
Run-Integration-Tests (3.9, 2.4)
Process completed with exit code 127.
Run-Integration-Tests (3.10, 2.7)
Process completed with exit code 127.
Run-Integration-Tests (3.10, 2.8)
Process completed with exit code 127.
Run-Integration-Tests (3.9, 2.7)
Process completed with exit code 127.
Run-Unit-Tests (3.11, 2.10)
Process completed with exit code 1.
Run-Integration-Tests (3.9, 2.5)
Process completed with exit code 127.
Run-Integration-Tests (3.9, 2.3)
Process completed with exit code 127.
Run-Unit-Tests (3.11, 2.8)
Process completed with exit code 1.
Run-Unit-Tests (3.11, 2.7)
Process completed with exit code 1.
Run-Unit-Tests (3.10, 2.9)
Process completed with exit code 1.
Run-Unit-Tests (3.10, 2.4)
Process completed with exit code 1.
Run-Unit-Tests (3.12, 2.10)
Process completed with exit code 1.
Run-Unit-Tests (3.9, 2.10)
Process completed with exit code 1.
Run-Unit-Tests (3.9, 2.4)
Process completed with exit code 1.
Run-Unit-Tests (3.11, 2.9)
Process completed with exit code 1.
Run-Unit-Tests (3.10, 2.3)
Process completed with exit code 1.
Run-Unit-Tests (3.8, 2.2)
Process completed with exit code 1.
Run-Unit-Tests (3.8, 2.5)
Process completed with exit code 1.
Run-Unit-Tests (3.8, 2.9)
Process completed with exit code 1.
Run-Unit-Tests (3.12, 2.9)
Process completed with exit code 1.
Run-Unit-Tests (3.8, 2.10)
Process completed with exit code 1.
Run-Unit-Tests (3.9, 2.3)
Process completed with exit code 1.
Run-Unit-Tests (3.10, 2.7)
Process completed with exit code 1.
Run-Unit-Tests (3.8, 2.8)
Process completed with exit code 1.
Run-Unit-Tests (3.10, 2.5)
Process completed with exit code 1.
Run-Unit-Tests (3.9, 2.6)
Process completed with exit code 1.
Run-Unit-Tests (3.9, 2.7)
Process completed with exit code 1.
Run-Unit-Tests (3.8, 2.3)
Process completed with exit code 1.
Run-Unit-Tests (3.10, 2.6)
Process completed with exit code 1.
Run-Unit-Tests (3.8, 2.7)
Process completed with exit code 1.
Run-Unit-Tests (3.9, 2.9)
Process completed with exit code 1.
Run-Unit-Tests (3.10, 2.8)
Process completed with exit code 1.
Run-Unit-Tests (3.8, 2.6)
Process completed with exit code 1.
Run-Unit-Tests (3.8, 2.4)
Process completed with exit code 1.
Run-Unit-Tests (3.9, 2.5)
Process completed with exit code 1.
Run-Unit-Tests (3.9, 2.2)
Process completed with exit code 1.
Run-Unit-Tests (3.9, 2.8)
Process completed with exit code 1.
Run-Integration-Tests (3.12, 2.10)
Process completed with exit code 127.
Run-Integration-Tests (3.11, 2.9)
Process completed with exit code 127.
Run-Integration-Tests (3.9, 2.9)
Process completed with exit code 127.
Run-Integration-Tests (3.9, 2.8)
Process completed with exit code 127.
Run-Unit-Tests (3.10, 2.10)
Process completed with exit code 1.
Run-Unit-Tests (3.11, 2.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.11, 2.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.11, 2.7)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.10, 2.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.10, 2.4)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.12, 2.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.9, 2.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.9, 2.4)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.11, 2.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.10, 2.3)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.8, 2.2)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.8, 2.5)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.8, 2.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.12, 2.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.8, 2.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.9, 2.3)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.10, 2.7)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.8, 2.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.10, 2.5)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.9, 2.6)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.9, 2.7)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.8, 2.3)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.10, 2.6)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.8, 2.7)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.9, 2.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.10, 2.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.8, 2.6)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.8, 2.4)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.9, 2.5)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.9, 2.2)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.9, 2.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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-Unit-Tests (3.10, 2.10)
The following actions use a deprecated Node.js version and will be forced to run on node20: 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/