| 2022-08-19 15:13:35 |
Dan Ryan |
description |
I have recently encountered build failures when building packages using lpcraft which write many logs to stdout during a short time interval which trigger the following error:
error: [Errno 11] write could not complete without blocking
2022-08-19 14:07:24.335 :: Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
2022-08-19 14:07:24.335 :: BlockingIOError: [Errno 11] write could not complete without blocking
2022-08-19 14:07:24.335 :: ldItalic
Log is here:
https://i619063024.restricted.launchpadlibrarian.net/619063024/buildlog_ci_jupyter-notebook_cd65fdd36c4fa1f328abbf32c8934447debbf598_BUILDING.txt.gz
Note that this build succeeds if I pipe stdout to devnull |
I have recently encountered build failures when building packages using lpcraft which write many logs to stdout during a short time interval which trigger the following error:
error: [Errno 11] write could not complete without blocking
2022-08-19 14:07:24.335 :: Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
2022-08-19 14:07:24.335 :: BlockingIOError: [Errno 11] write could not complete without blocking
2022-08-19 14:07:24.335 :: ldItalic
Log is here:
https://i619063024.restricted.launchpadlibrarian.net/619063024/buildlog_ci_jupyter-notebook_cd65fdd36c4fa1f328abbf32c8934447debbf598_BUILDING.txt.gz
Note that this build succeeds if I pipe stdout to devnull
A relevant detail may be that this build invokes npm to build documentation which logs quite heavily to stdout. |
|
