make sure annotations are initialized for AP #405
pr-created.yaml
on: pull_request
pr-created
/
...
/
check if secrets are set
0s
pr-created
/
...
/
Create cross-platform build
8m 17s
pr-created
/
...
/
Basic-Test
5m 48s
Annotations
17 errors and 4 warnings
pr-created / test / Basic-Test
Bad response: 422 {"message":"Couldn't find a repository matching this job.","error":true}
|
relevancy_golang:
results_xml_format/relevancy_golang.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
relevancy_fix_vuln:
results_xml_format/relevancy_fix_vuln.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
relevancy_enabled_stop_sniffing:
results_xml_format/relevancy_enabled_stop_sniffing.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
relevantCVEs:
results_xml_format/relevantCVEs.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
network_policy_known_servers:
results_xml_format/network_policy_known_servers.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
relevancy_golang_dynamic:
results_xml_format/relevancy_golang_dynamic.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
relevant_data_is_appended:
results_xml_format/relevant_data_is_appended.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
relevancy_python:
results_xml_format/relevancy_python.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
relevancy_java:
results_xml_format/relevancy_java.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
network_policy:
configurations/system/__pycache__/network_policy.cpython-38.pyc#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
relevancy_extra_large_image:
results_xml_format/relevancy_extra_large_image.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
relevancy_large_image:
results_xml_format/relevancy_large_image.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
network_policy_multiple_replicas:
results_xml_format/network_policy_multiple_replicas.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
relevancy_java_and_python:
results_xml_format/relevancy_java_and_python.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
network_policy_pod_restarted:
results_xml_format/network_policy_pod_restarted.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
network_policy_data_appended:
results_xml_format/network_policy_data_appended.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 8
|
pr-created / test / Create cross-platform build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4, 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-created / test / Create cross-platform build
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-created / test / Create cross-platform build
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-created / test / Basic-Test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v4, golangci/golangci-lint-action@v3, coverallsapp/github-action@v1, peter-evans/create-or-update-comment@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|