Skip to content
Pull Requests

Introduce 'ip' field to unit data in ingress relation v2 #739

Sign in to view logs

Introduce 'ip' field to unit data in ingress relation v2

Introduce 'ip' field to unit data in ingress relation v2 #739

Triggered via pull request October 18, 2023 10:32
@weiiwang01weiiwang01
synchronize #220
weiiwang01:feature/ips_in_ingress_v2
Status Failure
Total duration 46m 20s
Artifacts –

pull-request.yaml

on: pull_request
PR  /  Check against ignorelist
6s
PR / Check against ignorelist
PR  /  ...  /  Static Analysis of Libs
30s
PR / Quality Checks / Static Analysis / Static Analysis of Libs
PR  /  ...  /  Static Analysis of Charm
32s
PR / Quality Checks / Static Analysis / Static Analysis of Charm
PR  /  ...  /  Lint
15s
PR / Quality Checks / Linting / Lint
PR  /  ...  /  Unit tests
1m 43s
PR / Quality Checks / Unit Tests / Unit tests
PR  /  ...  /  Scenario tests
58s
PR / Quality Checks / Scenario Tests / Scenario tests
PR  /  ...  /  Check the CHARMHUB_TOKEN secret
PR / Quality Checks / Check the CHARMHUB_TOKEN secret
PR  /  ...  /  check
7s
PR / Quality Checks / Inclusive naming / check
Matrix: PR / Quality Checks / CodeQL analysis / Analyze
Waiting for pending jobs
PR  /  ...  /  Integration Tests
PR / Quality Checks / Integration Tests / Integration Tests
PR  /  ...  /  Check libraries
0s
PR / Quality Checks / Check libraries
Fit to window
Zoom out
Zoom in

Annotations

4 errors
PR / Quality Checks / Static Analysis / Static Analysis of Libs
Process completed with exit code 1.
PR / Quality Checks / Linting / Lint
Process completed with exit code 1.
PR / Quality Checks / Scenario Tests / Scenario tests
Process completed with exit code 1.
PR / Quality Checks / Unit Tests / Unit tests
Process completed with exit code 1.