Chris Johns created an issue: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/issues/27
Assignee: Chris Johns ## Summary Running `rtems-test` with `--rtems-bsp=xilinx_zynq_a9_qemu --timeout 40` and the options to get all the exes results in a `BlockingIOError` to happen in a place Python cannot raise it. I have investigated this and it is happening `log.py` when under load. You can trip it by adding `--trace` to the options. The file descriptor is `stdout` and it is in non-blocking mode. Nothing in the `tester` directory or `rtemstoolskit` sets `stdout` to non-blocking. I found it happens when `subprocess.Popen` returns from when calling `qemu`. I have not been able to determine the reason for this. ## Steps to reproduce See above. # Fix It seems checking the file descriptor on a log write to see if it is non-blocking fixes the problem. This is pretty hack'ish. I wonder if changing the blocking mode when the exception happens would be. I will check this as well. -- View it on GitLab: https://gitlab.rtems.org/rtems/tools/rtems-tools/-/issues/27 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs
