Skip to content
Node Agent Component Tests

Improving rule r0006 #684

Sign in to view logs

Improving rule r0006

Improving rule r0006 #684

Triggered via pull request November 24, 2024 11:53
@amitschendelamitschendel
synchronize #410
feature/improve-rule
Status Success
Total duration 18m 31s
Artifacts –

component-tests.yaml

on: pull_request
build-and-push-image
2m 22s
build-and-push-image
Matrix: component-tests
Fit to window
Zoom out
Zoom in

Annotations

16 errors and 12 warnings
relevancy_python: results_xml_format/relevancy_python.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 9
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: 9
relevancy_golang: results_xml_format/relevancy_golang.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 9
relevancy_large_image: results_xml_format/relevancy_large_image.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 9
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: 9
network_policy: configurations/system/__pycache__/network_policy.cpython-38.pyc#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 9
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: 9
relevancy_golang_dynamic: results_xml_format/relevancy_golang_dynamic.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 9
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: 9
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: 9
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: 9
relevancy_java: results_xml_format/relevancy_java.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 9
relevantCVEs: results_xml_format/relevantCVEs.xml#L1
wrong number of pods are running after 360 seconds. expected: 10, running: 9
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: 9
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: 9
relevancy_fix_vuln: results_xml_format/relevancy_fix_vuln.xml#L1
get_filtered_SBOM_from_storage, timeout: 6 minutes, error: (404) Reason: Not Found
component-tests (Test_07_RuleBindingApplyTest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
component-tests (Test_08_ApplicationProfilePatching)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
component-tests (Test_11_EndpointTest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
component-tests (Test_06_KillProcessInTheMiddle)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
component-tests (Test_10_MalwareDetectionTest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
component-tests (Test_01_BasicAlertTest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
component-tests (Test_12_MergingProfilesTest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
component-tests (Test_13_MergingNetworkNeighborhoodTest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
component-tests (Test_02_AllAlertsFromMaliciousApp)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
component-tests (Test_14_RulePoliciesTest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
component-tests (Test_03_BasicLoadActivities)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
component-tests (Test_05_MemoryLeak_10K_Alerts)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/