Pipeline failure and possible solution

Pipeline is halted, or taking an exceptionally long time to execute:

Problem: In RCPP domain (BMW Retailer Hub) pipeline was halting at the same test batch until timeout and previously had issue of waiting in a different test batch for hours before continuing the execution. In case of checking on the node it can be seen, that Chrome browsers were not popping up anymore, so the UI test were not being executed, this can be seen in the log that by the time the hang happend the tests were already finished.

Possible cause:The problem possibly was the logs sent to default output after execution were overburdening the process which (not known if given enough time it would have finished). Part of the problem my be that in this case batch contained 30+ tests, and about half of them failed, in which case a screenshot is taken, and in a base64 coded format it was printed to the logs, adding considerable amount of lines to the logs.

Possible fix: Adding the “-l filename.log” attribute to the maven cmd line in the workflow.yml solved the issue, this way not sending logs directly to the default output but instead saved on the node in the “filename.log”.

Other things that can be tried out in similar case:
-Trying to disable logging about the test execution as a whole, and verifying if that solves the problem
-Changing the logback to not include the screenshots (removing the lines about TMS such as screenshot, api calls)
-Reducing the amount of tests, possibly commenting out failing ones, to see if the the logging is the issue.