Skip to content
Pull Requests

fixed scenario tests and made pyright checks stricter #71

Sign in to view logs

fixed scenario tests and made pyright checks stricter

fixed scenario tests and made pyright checks stricter #71

Triggered via pull request January 5, 2024 13:58
@PietroPasottiPietroPasotti
synchronize #24
param_type_checking
Status Failure
Total duration 9m 40s
Artifacts 2

pull-request.yaml

on: pull_request
PR  /  Check against ignorelist
4s
PR / Check against ignorelist
PR  /  ...  /  Static Analysis of Libs
13s
PR / Quality Checks / Static Analysis / Static Analysis of Libs
PR  /  ...  /  Static Analysis of Charm
13s
PR / Quality Checks / Static Analysis / Static Analysis of Charm
PR  /  ...  /  Lint
11s
PR / Quality Checks / Linting / Lint
PR  /  ...  /  Unit tests
12s
PR / Quality Checks / Unit Tests / Unit tests
PR  /  ...  /  Scenario tests
11s
PR / Quality Checks / Scenario Tests / Scenario tests
PR  /  ...  /  Check the CHARMHUB_TOKEN secret
0s
PR / Quality Checks / Check the CHARMHUB_TOKEN secret
PR  /  ...  /  check
7s
PR / Quality Checks / Inclusive naming / check
Matrix: PR / Quality Checks / CodeQL analysis / Analyze
PR  /  ...  /  Integration Tests
8m 55s
PR / Quality Checks / Integration Tests / Integration Tests
PR  /  ...  /  Check libraries
34s
PR / Quality Checks / Check libraries
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
PR / Quality Checks / Integration Tests / Integration Tests
Command microk8s kubectl auth can-i create pods --as=me failed 12 times, giving up
PR / Quality Checks / Integration Tests / Integration Tests
Process completed with exit code 1.
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.

Artifacts

Produced during runtime
Name Size
charmcraft-logs Expired
60.4 KB
juju-crashdump Expired
2.44 KB