Joonas Kuisma
Joonas Kuisma
The issue is that if the port is the default `8270` or any user-specified port (`!= 0`), its availability is currently not checked, which can lead to the problem described....
I realized that raising an error was actually a poor choice for pabot's own parallel pytest CI test runs. 😆 The implementation was updated so that if a reserved port...
Hi @jkeset and @hfy1111 ! Thanks for the observations! I was able to reproduce the issue and investigate the root cause. The problem is that the current implementation terminates only...
Hi @jkeset ! The issue should be resolved by updating to Robot Framework version 7.0.1 or later. Have you still encountered this issue, or could we go ahead and close...
Hi @DirkRichter ! I looked into this issue, and fixing it is very difficult with the current implementation. The problem arises from how Robot and Pabot handle datasources and how...
Hi! This is actually about two slightly different issues, so I’ll start by replying to the original @PaulTr16 question. I believe the reason the tests run successfully when executed serially...
Edited title because this should be more like a question, not a bug.
Hi @Brownies ! That’s indeed true and is caused by the Robot Framework’s RemoteLibrary used by Pabot. It's due to the limitations of the XML-RPC protocol, which unfortunately can’t really...
Hi! Is this issue still relevant? If so, could you kindly provide more details about it — such as the conditions under which it occurs, the command used, the structure...
Hi @jvrfaria ! I’ll need to take a closer look at this issue at some point. It’s possible that the command is somehow incomplete or interrupted. However, I’ll link issue...