Skip to content

Fix frame names in the allocation table for simple GT job #16468

Fix frame names in the allocation table for simple GT job

Fix frame names in the allocation table for simple GT job #16468

Triggered via pull request November 28, 2024 16:17
Status Success
Total duration 53m 11s
Artifacts 6

main.yml

on: pull_request
search_cache  /  search_cache
5s
search_cache / search_cache
Matrix: e2e_testing
publish_dev_images
0s
publish_dev_images
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Variables should be defined before their use: Dockerfile#L96
UndefinedVar: Usage of undefined variable '$no_proxy' More info: https://docs.docker.com/go/dockerfile/rule/undefined-var/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L148
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Sensitive data should not be used in the ARG or ENV commands: Dockerfile.ui#L31
SecretsUsedInArgOrEnv: Do not use ARG or ENV instructions for sensitive data (ARG "SOURCE_MAPS_TOKEN") More info: https://docs.docker.com/go/dockerfile/rule/secrets-used-in-arg-or-env/

Artifacts

Produced during runtime
Name Size
coverage_results
6.12 MB
cvat-ai~cvat~DOG3O1.dockerbuild
84.4 KB
cvat-ai~cvat~VRAZ4S.dockerbuild
43.4 KB
cvat_sdk
961 KB
cvat_server
398 MB
cvat_ui
35.9 MB