server/process: Avoid tracebacks at exit
PATCH 1/1 server/process: Avoid tracebacks at exit
In theory this should have been worked around but is still occurring. Add it to the list of things to ignore when bitbake is shutting down.
Traceback (most recent call last):
File "/usr/lib64/python3.9/threading.py", line 973, in _bootstrap_inner
self.run()
File "/home/pokybuild/yocto-worker/oe-selftest-fedora/build/bitbake/lib/bb/server/process.py", line 698, in startCallbackHandler
event = self.reader.get()
File "/home/pokybuild/yocto-worker/oe-selftest-fedora/build/bitbake/lib/bb/server/process.py", line 722, in get
res = self.reader.recv_bytes()
File "/usr/lib64/python3.9/multiprocessing/connection.py", line 221, in recv_bytes
buf = self._recv_bytes(maxlength)
File "/usr/lib64/python3.9/multiprocessing/connection.py", line 426, in _recv_bytes
return self._recv(size)
File "/usr/lib64/python3.9/multiprocessing/connection.py", line 384, in _recv
chunk = read(handle, remaining)
TypeError: an integer is required (got type NoneType)'
--- lib/bb/server/process.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
lib/bb/server/process.py +1 -1
@@ -697,7 +697,7 @@ class BBUIEventQueue: if ready: event = self.reader.get() self.queue_event(event) - except (EOFError, OSError): + except (EOFError, OSError, TypeError): # Easiest way to exit is to close the file descriptor to cause an exit break
Signature · 1 line
2.34.1