The report-portal.js plugin procreates an enormous amount of processes during execution

[epam-avramenko]

While executing Cypress Tests and integrating with Reportal Portal via report-portal.js, we encountered a significant issue involving the generation of a large number of hanging processes, as depicted in the image below. Towards the end of the execution, the count of these processes can surge to over 30 thousand, causing a degradation in system performance.

The hung-up processes are like ./cache/12.0.0/Cypress/Cypress ./node_modules/@reportportal/agent-js-cypress/lib/worker.js

Therefore, the question is: Does anyone know what the problem is?

[epam-avramenko]

After conducting additional investigation, it was found that the issue originates from a significant flaw in the integration plugin for Report Portal. This issue occurs when results are being sent via a single launch ID, causing a separate process to be initiated for each test. These processes then remain hung during the entire test execution.
Therefore, a workaround solution was found after further investigation and many tests. The plugin contains an approach that allows starting a standalone launch for each test in the test suite. This leads to a side effect of a vast number of launches for each pipeline execution, but in the case of defining proper prompt parameters, the plugin merges all of those launches and their results into one launch at the end of execution. However, a precise combination of parameters has to be passed to achieve that effect.