Skip to content
Linting

Use Gingko spec labels in E2E tests #4266

Sign in to view logs

Use Gingko spec labels in E2E tests

Use Gingko spec labels in E2E tests #4266

Triggered via pull request October 17, 2023 14:48
@tpantelistpantelis
synchronize #2756
tpantelis:e2e_ginkgo_labels
Status Success
Total duration 5m 32s
Artifacts –

linting.yml

on: pull_request
No "Apply suggestions from code review" Commits
4s
No "Apply suggestions from code review" Commits
Submariner K8s API Code Generation
4m 40s
Submariner K8s API Code Generation
Protobuf Code Generation
41s
Protobuf Code Generation
Commit Message(s)
14s
Commit Message(s)
Go
5m 17s
Go
Dependency Licenses
3m 8s
Dependency Licenses
Markdown Links (modified files)
17s
Markdown Links (modified files)
Markdown
11s
Markdown
Package Documentation
1m 14s
Package Documentation
Shell
14s
Shell
Variant Analysis
5m 19s
Variant Analysis
Vulnerability Scanning
34s
Vulnerability Scanning
YAML
13s
YAML
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
No "Apply suggestions from code review" Commits
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Variant Analysis
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
Variant Analysis
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.14.6.
Variant Analysis
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.