Skip to content
This repository has been archived by the owner on Oct 8, 2024. It is now read-only.
Pull Requests

Add tempo-ready service for interface tests #451

Sign in to view logs

Add tempo-ready service for interface tests

Add tempo-ready service for interface tests #451

Triggered via pull request September 1, 2024 11:30
@mmkaymmkay
synchronize #164
interface-fix
Status Success
Total duration 32m 46s
Artifacts –

pull-request.yaml

on: pull_request
PR  /  Check against ignorelist
3s
PR / Check against ignorelist
PR  /  ...  /  Static Analysis of Libs
27s
PR / Quality Checks / Static Analysis / Static Analysis of Libs
PR  /  ...  /  Static Analysis of Charm
20s
PR / Quality Checks / Static Analysis / Static Analysis of Charm
PR  /  ...  /  Lint
13s
PR / Quality Checks / Linting / Lint
PR  /  ...  /  Unit tests
16s
PR / Quality Checks / Unit Tests / Unit tests
PR  /  ...  /  Scenario tests
27s
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
31m 51s
PR / Quality Checks / Integration Tests / Integration Tests
PR  /  ...  /  Check libraries
26s
PR / Quality Checks / Check libraries
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
PR / Quality Checks / Linting / Lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PR / Quality Checks / Unit Tests / Unit tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PR / Quality Checks / Static Analysis / Static Analysis of Charm
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PR / Quality Checks / Static Analysis / Static Analysis of Libs
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PR / Quality Checks / Scenario Tests / Scenario tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-python@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
PR / Quality Checks / CodeQL analysis / Analyze (python)
The following actions use a deprecated Node.js version and will be forced to run on node20: github/codeql-action/init@v2, github/codeql-action/autobuild@v2, github/codeql-action/analyze@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
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.