Skip to content
Benchmark

Fix the issue of missing container information caused by the event sequence when docker compose is repeatedly up. #47

Sign in to view logs

Fix the issue of missing container information caused by the event sequence when docker compose is repeatedly up.

Fix the issue of missing container information caused by the event sequence when docker compose is repeatedly up. #47

Triggered via pull request November 13, 2024 02:15
@linrunqi08linrunqi08
closed #1875
feature/taiye/fix_docker_compose_container_info
Status Success
Total duration 35m 41s
Artifacts –

benchmark.yaml

on: pull_request
Matrix: CI
result
0s
result
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
CI (1.19.10, 3.8, ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
CI (1.19.10, 3.8, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/