Skip to content

Workaround: observe relation changed directly #222

Workaround: observe relation changed directly

Workaround: observe relation changed directly #222

Triggered via pull request December 1, 2024 01:49
Status Success
Total duration 21m 53s
Artifacts

pull-request.yaml

on: pull_request
PR  /  Check against ignorelist
5s
PR / Check against ignorelist
PR  /  ...  /  Static Analysis of Libs
20s
PR / Quality Checks / Static Analysis / Static Analysis of Libs
PR  /  ...  /  Static Analysis of Charm
14s
PR / Quality Checks / Static Analysis / Static Analysis of Charm
PR  /  ...  /  Lint
9s
PR / Quality Checks / Linting / Lint
PR  /  ...  /  Unit tests
15s
PR / Quality Checks / Unit Tests / Unit tests
PR  /  ...  /  Scenario tests
7s
PR / Quality Checks / Scenario Tests / Scenario tests
PR  /  ...  /  Check the CHARMHUB_TOKEN secret
0s
PR / Quality Checks / Check the CHARMHUB_TOKEN secret
PR  /  ...  /  check
5s
PR / Quality Checks / Inclusive naming / check
Matrix: PR / Quality Checks / CodeQL analysis / Analyze
PR  /  ...  /  Integration Tests
21m 8s
PR / Quality Checks / Integration Tests / Integration Tests
PR  /  ...  /  Check libraries
20s
PR / Quality Checks / Check libraries
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
PR / Quality Checks / CodeQL analysis / Analyze (python)
CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/
PR / Quality Checks / CodeQL analysis / Analyze (python)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
PR / Quality Checks / CodeQL analysis / Analyze (python)
Unable to validate code scanning workflow: MissingPushHook