Status: Accepted
Owner: pekka.klarck
Labels: Target-2.8.4 Priority-Medium Type-Defect
New issue 1640 by pekka.klarck: Process: Reading output from custom streams
sometimes fails with Jython on Windows
http://code.google.com/p/robotframework/issues/detail?id=1640
This bug represents itself two different ways:
1) Reading output from given custom stdout/stderr fails so that only an
empty string is got. This doesn't normally happen too often, but it is
nevertheless easy to reproduce by executing Run Process with custom
stdout/stderr repeatedly e.g. in a for loop.
2) If a huge amount of output is written, reading custom stdout/stderr can
hang.
The root cause for these problems is that custom streams are read before
all output from processes is written to them. A fix is keeping a handle to
those streams and flushing/closing them before opening them again for
reading.
I've only seen these problems with Jython on Windows, but based on the root
cause analysis they could occur also elsewhere.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to robotframework-commit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
