Skip to content

fix: docker compose port change #100288

fix: docker compose port change

fix: docker compose port change #100288

Triggered via pull request October 7, 2024 23:37
Status Failure
Total duration 6h 1m 19s
Artifacts

ci-backend.yml

on: pull_request
Determine need to run backend checks
6s
Determine need to run backend checks
Matrix: async-migrations
Matrix: django
Python code quality checks
2m 49s
Python code quality checks
Validate Django and CH migrations
3m 10s
Validate Django and CH migrations
Calculate running time
0s
Calculate running time
Fit to window
Zoom out
Zoom in

Annotations

23 errors and 3 warnings
Django tests – Core (persons-on-events on), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (4/10)
The job running on runner GitHub Actions 380 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events on), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (7/10)
The job running on runner GitHub Actions 271 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events on), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (3/10)
The job running on runner GitHub Actions 82 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events on), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (1/10)
The job running on runner GitHub Actions 466 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events on), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (5/10)
The job running on runner GitHub Actions 404 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events on), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (9/10)
The job running on runner GitHub Actions 193 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events off), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (1/10)
The job running on runner GitHub Actions 409 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events off), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (8/10)
The job running on runner GitHub Actions 172 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events off), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (6/10)
The job running on runner GitHub Actions 399 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events off), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (2/10)
The job running on runner GitHub Actions 83 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events off), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (7/10)
The job running on runner GitHub Actions 382 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events off), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (9/10)
The job running on runner GitHub Actions 86 has exceeded the maximum execution time of 30 minutes.
Django tests – Temporal (persons-on-events off), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (1/1)
The job running on runner GitHub Actions 330 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events off), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (3/10)
The job running on runner GitHub Actions 31 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events on), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (6/10)
The job running on runner GitHub Actions 295 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events off), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (10/10)
The job running on runner GitHub Actions 69 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events off), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (5/10)
The job running on runner GitHub Actions 77 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events on), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (10/10)
The job running on runner GitHub Actions 232 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events on), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (2/10)
The job running on runner GitHub Actions 389 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events on), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (8/10)
The job running on runner GitHub Actions 288 has exceeded the maximum execution time of 30 minutes.
Django tests – Core (persons-on-events off), Py 3.11.9, clickhouse/clickhouse-server:23.12.6.19 (4/10)
The job running on runner GitHub Actions 488 has exceeded the maximum execution time of 30 minutes.
Async migrations tests - clickhouse/clickhouse-server:23.12.6.19
The job running on runner GitHub Actions 355 has exceeded the maximum execution time of 360 minutes.
Async migrations tests - clickhouse/clickhouse-server:23.12.6.19
The operation was canceled.
Determine need to run backend checks
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, dorny/paths-filter@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Python code quality checks
The following actions use a deprecated Node.js version and will be forced to run on node20: n1hility/cancel-previous-runs@v3, actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Validate Django and CH migrations
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/