I think the problem is that Robot Framework has some internal global
state (related to logging in this case). And when you are jumping over
a process boundary the internal state is totally different for the
other process.
The safest way in my opinion would be not to import anything from
robot in the module your going to run in the other process.
You could also use threading and then the shared state would be "OK"
.. but only if nothing CPU intensive is required (because of the GIL).
Kind Regards,
Mikko Korpela
> --
> You received this message because you are subscribed to the Google Groups "robotframework-users" group.
> To post to this group, send email to robotframe...@googlegroups.com.
> To unsubscribe from this group, send email to robotframework-u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/robotframework-users?hl=en.
>
--
Mikko Korpela