Implementing Service Discovery Backend #287
pr-created.yaml
on: pull_request
pr-created
/
...
/
check if secrets are set
0s
pr-created
/
...
/
Create cross-platform build
13m 40s
pr-created
/
...
/
Basic-Test
4m 30s
Annotations
26 errors and 2 warnings
pr-created / test / Basic-Test
Resource not accessible by integration
|
pr-created / test / Basic-Test
See this action's readme for details about this error
|
pr-created / test / Basic-Test
Cannot open: File exists
|
pr-created / test / Basic-Test
Cannot open: File exists
|
pr-created / test / Basic-Test
Cannot open: File exists
|
pr-created / test / Basic-Test
Cannot open: File exists
|
pr-created / test / Basic-Test
Cannot open: File exists
|
pr-created / test / Basic-Test
Cannot open: File exists
|
pr-created / test / Basic-Test
Cannot open: File exists
|
pr-created / test / Basic-Test
Cannot open: File exists
|
pr-created / test / Basic-Test
Cannot open: File exists
|
pr-created / test / Basic-Test
Cannot open: File exists
|
pr-created / test / Basic-Test
Process completed with exit code 1.
|
vulnerability_scanning:
results_xml_format/vulnerability_scanning.xml#L1
wrong number of pods are running after 180 seconds. expected: 8, running: 7
|
relevancy_golang_dynamic:
results_xml_format/relevancy_golang_dynamic.xml#L1
wrong number of pods are running after 360 seconds. expected: 9, 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: 9, 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: 9, running: 8
|
relevancy_java:
results_xml_format/relevancy_java.xml#L1
wrong number of pods are running after 360 seconds. expected: 9, running: 8
|
relevantCVEs:
results_xml_format/relevantCVEs.xml#L1
wrong number of pods are running after 360 seconds. expected: 9, 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: 9, running: 8
|
relevancy_fix_vuln:
results_xml_format/relevancy_fix_vuln.xml#L1
wrong number of pods are running after 360 seconds. expected: 9, 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: 9, running: 8
|
relevancy_golang:
results_xml_format/relevancy_golang.xml#L1
wrong number of pods are running after 360 seconds. expected: 9, running: 8
|
vulnerability_scanning_cve_exceptions:
results_xml_format/vulnerability_scanning_cve_exceptions.xml#L1
wrong number of pods are running after 360 seconds. expected: 8, running: 7
|
relevancy_python:
results_xml_format/relevancy_python.xml#L1
wrong number of pods are running after 360 seconds. expected: 9, running: 8
|
relevancy_large_image:
results_xml_format/relevancy_large_image.xml#L1
wrong number of pods are running after 360 seconds. expected: 9, running: 8
|
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
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
|