-
Type: Task
-
Status: To Do (View Workflow)
-
Priority: Low
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Testing
-
Labels:None
-
Story Points:0
https://jenkins.opencord.org/job/periodic-voltha-pm-data-test-bbsim/812/console
[2023-07-21T10:54:23.875Z] Successfully built robotframework-kafkalibrary robotframework-lint robotframework-sshlibrary cord-robot robotframework-importresource voltha-protos protobuf3-to-dict device-management-interface robotlibcore-temp wrapt
[2023-07-21T10:54:30.967Z] set +u && source .venv/bin/activate && set -u \ [2023-07-21T10:54:30.967Z] && tests/pm-data \ [2023-07-21T10:54:30.967Z] && robot -V /w/workspace/periodic-voltha-pm-data-test-bbsim/voltha-system-tests/tests/data/bbsim-kind.yaml -V /w/workspace/periodic-voltha-pm-data-test-bbsim/voltha-system-tests/tests/data/pm-data.yaml -d /w/workspace/periodic-voltha-pm-data-test-bbsim/voltha-pm-data-single-kind-att -v ONOS_SSH_PORT:30115 -v ONOS_REST_PORT:30120 -v NAMESPACE:voltha -v INFRA_NAMESPACE:default -v container_log_dir:/w/workspace/periodic-voltha-pm-data-test-bbsim/voltha-pm-data-single-kind-att -v logging:True -v workflow:ATT -i functional -e PowerSwitch Voltha_ONUPMTests.robot [2023-07-21T10:54:30.967Z] bash: line 2: tests/pm-data: Is a directory [2023-07-21T10:54:30.967Z] Makefile:568: recipe for target 'voltha-pm-data-test' failed [2023-07-21T10:54:30.967Z] make: *** [voltha-pm-data-test] Error 126
[2023-07-21T10:54:33.904Z] [Pipeline] step [2023-07-21T10:54:33.944Z] Robot results publisher started... [2023-07-21T10:54:33.944Z] -Parsing output xml: [2023-07-21T10:54:34.074Z] Failed! [2023-07-21T10:54:34.074Z] hudson.AbortException: No files found in path /w/workspace/periodic-voltha-pm-data-test-bbsim with configured filemask: **/*/output*.xml [2023-07-21T10:54:34.074Z] at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:76) [2023-07-21T10:54:34.074Z] at hudson.plugins.robot.RobotParser$RobotParserCallable.invoke(RobotParser.java:52)
- Debug test/pm-data failure in voltha-pm-data-test
- Why did the jenkins job not exit immediately after the test failure ?
- Test run is basically garbage due to early failure.
- Jenkins should fail hard on this condition.
- All processing stops, jenkins moves onto the next job.