Status: Accepted
Owner: ----
Labels: Target-2.5.5 Priority-High Type-Enhancement
New issue 697 by pekka.klarck: Log messages and failures from threads
executed by library are not visible
http://code.google.com/p/robotframework/issues/detail?id=697
This problem was reported on NSN mailing lists and the original discussion
is below. We need to investigate can we do something about it.
Juha L. wrote:
We use Robot Framework 2.1.2 (Jython 2.5.1 on java1.5.0_22). We have class
A which is created from Robot and system.out seems to work fine from that.
But in the other class which is runing in a Thread which is created by
class A, the system.out doesnt' seem to go for the Robot log. What could be
the problem?
Ossi K. replied:
We noticed the same thing with python threads when developing plain cpython
robot library some time back. This appears to be some feature in Robot's
way of invoking library keywords. Our workaround was to store worker
thread's output to a thread local variable where it is read by the main
thread after joining the worker thread because our output was not stirctly
needed in real time.
Aki H. replied:
We have the same problem too. It also means that if we run to an assertion
error in a thread, the assertion string is not logged. We have implemented
the workaround that Ossi suggested for assertions, but we still lose the
other loggings.
