Skip to content
CI

Rename CLI commands for clarity #392

Sign in to view logs

Rename CLI commands for clarity

Rename CLI commands for clarity #392

Triggered via pull request February 25, 2025 14:25
@camille-bouvy-frequenzcamille-bouvy-frequenz
synchronize #108
camille-bouvy-frequenz:rename-cli-commands
Status Success
Total duration 3m 46s
Artifacts 3

ci.yaml

on: pull_request
Matrix: Cross-arch tests with nox
Matrix: Test with nox
Build distribution packages
15s
Build distribution packages
Test documentation website generation
34s
Test documentation website generation
Cross-arch tests with nox
0s
Cross-arch tests with nox
Test with nox
3s
Test with nox
Test package installation in different architectures
3m 13s
Test package installation in different architectures
Publish documentation website to GitHub pages
0s
Publish documentation website to GitHub pages
Create GitHub release
0s
Create GitHub release
Publish packages to PyPI
0s
Publish packages to PyPI
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
Build distribution packages
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Test documentation website generation
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Test with nox (ubuntu-20.04, 3.11, pytest_min)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Test with nox (ubuntu-20.04, 3.11, ci_checks_max)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Test with nox
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Test package installation in different architectures
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Setting platform to predefined $TARGETPLATFORM in FROM is redundant as this is the default behavior: .github/containers/test-installation/Dockerfile#L6
RedundantTargetPlatform: Setting platform to predefined ${TARGETPLATFORM} in FROM is redundant as this is the default behavior More info: https://docs.docker.com/go/dockerfile/rule/redundant-target-platform/
Test package installation in different architectures
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists

Artifacts

Produced during runtime
Name Size Digest
dist-packages Expired
62.8 KB
sha256:96cafb8c84ed9fee00d60154d964e8825db608b1988ba5c6bc79a7bfea486ce5
docs-site Expired
918 KB
sha256:0daea02442ee8a26d3adcc0fa566d6a57d147152424edc5b1c4109d1e677934c
frequenz-floss~frequenz-client-electricity-trading-python~20N1VL.dockerbuild Expired
49.3 KB
sha256:995b2bd887f24d719a323ec628cef752add6f859982a253f78854d1b9629a710