Skip to content
Backend CI

fix: docker compose port change #100273

Sign in to view logs

fix: docker compose port change

fix: docker compose port change #100273

Triggered via pull request October 7, 2024 20:50
@bciaraldibciaraldi
opened #25444
bciaraldi/2024_10_07-compose-adjustments
Status Cancelled
Total duration 2h 5m 2s
Artifacts –

ci-backend.yml

on: pull_request
Determine need to run backend checks
7s
Determine need to run backend checks
Matrix: async-migrations
Matrix: django
Python code quality checks
2m 45s
Python code quality checks
Validate Django and CH migrations
4m 0s
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 (1/10)
The job running on runner GitHub Actions 273 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 18 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 444 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 418 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 113 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 287 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 491 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 49 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 (4/10)
The job running on runner GitHub Actions 300 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 211 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 451 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 73 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 345 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 186 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 88 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 380 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 134 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 244 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 386 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 219 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 229 has exceeded the maximum execution time of 30 minutes.
Async migrations tests - clickhouse/clickhouse-server:23.12.6.19
The run was canceled by @bciaraldi.
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/