18 January 2026:
Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, API, windows and java based applications and SAP.
This forum is now archived and is in read-only mode. Please continue discussions on our improved new Sahi Pro Community forum.
Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, API, windows and java based applications and SAP.
Issue with running parallel sahi instances within same box
deepan
Members
Hi,
We use parallel instances of twist with sahi driver to run our regression builds. And we notice that often, one of the parallel instances kills the firefox instance of other parallel sahi instances. As per our understanding the way any sahi instance identifies the firefox browsers that it started (using the process command in os.properties) has some issue because we observed from the twist runner logs that one sahi instance collects process ids of firefox instances of other sahi runners
like, [twist.runner] INFO: PIDs: [13618, 13622, 13681, 13685, 13765, 13770]; 1569 ms
Is there a better way to handle this problem?
We use parallel instances of twist with sahi driver to run our regression builds. And we notice that often, one of the parallel instances kills the firefox instance of other parallel sahi instances. As per our understanding the way any sahi instance identifies the firefox browsers that it started (using the process command in os.properties) has some issue because we observed from the twist runner logs that one sahi instance collects process ids of firefox instances of other sahi runners
like, [twist.runner] INFO: PIDs: [13618, 13622, 13681, 13685, 13765, 13770]; 1569 ms
Is there a better way to handle this problem?
Comments
What you report may be because of incorrect synchronization while getting the PIDs. I will check with the Twist team and get back to you.
Regards,
Narayan