You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks, I can add set -v for future, but I suspect that rerun will fix it... I hoped you have some idea what could cause this error without rerunning the job.
I'm having this problem - here's an example where two different runs on the same code have different build failures, with no error message, just a stopped log:
These two builds run the exact same code a few 10s of minutes apart - just an empty commit difference between them - but have different matrix entries failing:
For example, in this job for Python 2.7, 32-bit, there is no error message in the log but the build failed. The same matrix entry passed with the same code, just adding an empty commit to trigger the build - see ok build.
This seems may well be happening for other projects too - there are new unexpected build failures, without matching errors, at:
I think this should not be closed, the bug is still at large, and popped up for us in the past few months.
Finding a workaround in a closed bug report is not what I would expect, maybe the stale bot shouldn't close the unresolved reports?
Reacted by David Hoese, Piotr Zurek, Fabian Nieto and Glauber M Dantas
Activity
DarthGandalf commentedon Dec 15, 2017
Update: it's not related to the update, because we use
group: deprecated-2017Q3BanzaiMan commentedon Dec 15, 2017
It is strange that https://travis-ci.org/znc/znc/jobs/316693823 ran on an image from July, https://travis-ci.org/znc/znc/jobs/316693823#L15 17 hours ago.
BanzaiMan commentedon Dec 15, 2017
oh, you specified it.
BanzaiMan commentedon Dec 15, 2017
Could you try setting the
verbosebash option to see if it yields any interesting information?set -v. Thanks.DarthGandalf commentedon Dec 15, 2017
Thanks, I can add
set -vfor future, but I suspect that rerun will fix it... I hoped you have some idea what could cause this error without rerunning the job.Add set -v to travis
DarthGandalf commentedon Dec 17, 2017
Hi, seeing new errors, which may or may not be related to the one above.
https://travis-ci.org/znc/znc/jobs/317632628 reports that a command failed without even trying to run that command, there is no
$ env ...string above it.https://travis-ci.org/znc/znc/jobs/317632629 and https://travis-ci.org/znc/znc/jobs/317632637 both say
make: write errorafter successfully doing what they were supposed to do.matthew-brett commentedon Dec 18, 2017
I'm having this problem - here's an example where two different runs on the same code have different build failures, with no error message, just a stopped log:
These two builds run the exact same code a few 10s of minutes apart - just an empty commit difference between them - but have different matrix entries failing:
For example, in this job for Python 2.7, 32-bit, there is no error message in the log but the build failed. The same matrix entry passed with the same code, just adding an empty commit to trigger the build - see ok build.
This seems may well be happening for other projects too - there are new unexpected build failures, without matching errors, at:
matthew-brett commentedon Dec 18, 2017
See also : MacPython/pandas-wheels#22 (comment)
avagin commentedon Dec 18, 2017
I see this error too. It is reproduced each time:
https://travis-ci.org/avagin/criu/builds/318207911
avagin commentedon Dec 18, 2017
I tried to debug this issue and run make under strace, but make is completed successfully in this case.
https://travis-ci.org/avagin/criu/builds/317936454
avagin commentedon Dec 19, 2017
I did a few experiments and I found that sometime programs fail to write on stdout.
https://travis-ci.org/avagin/linux/jobs/318414661
avagin commentedon Dec 19, 2017
A script is executed with stdout, for which O_NONBLOCK is set. It is obviously a bug.
avagin commentedon Dec 19, 2017
As a workaround, I added the following line in my test script:
Workaround for travis-ci/travis-ci#8920
38 remaining items
Update .travis.yml (#391)
znc: Autospec creation for update from version 1.6.6 to version 1.7.1
retorquere commentedon Apr 18, 2019
I'm still seeing this problem; all my builds fail with "write could not complete without blocking"
TheoLechemia commentedon Jul 16, 2019
Same probleme here. On Ubuntu 16.04
travis is broken
Possible fix for BlockingIOError: [Errno 11] write could not complete…
Possible fix for BlockingIOError: [Errno 11] write could not complete…
Possible fix for BlockingIOError: [Errno 11] write could not complete…
bsipocz commentedon Mar 2, 2020
I think this should not be closed, the bug is still at large, and popped up for us in the past few months.
Finding a workaround in a closed bug report is not what I would expect, maybe the stale bot shouldn't close the unresolved reports?
Travis failure workaround
Add travis workaround for long logs
Possible fix for BlockingIOError: [Errno 11] write could not complete…
Bug 1652286 - Firefox doc: Workaround the BlockingIOError error r=fir…
Bug 1652286 - Firefox doc: Workaround the BlockingIOError error r=fir…
Bug 1652286 - Firefox doc: Workaround the BlockingIOError error r=fir…