Red Hat Bugzilla – Bug 1257181
[abrt] mock: util.py:361:logOutput:OSError: [Errno 5] Input/output error
Last modified: 2015-09-04 03:09:18 EDT
Version-Release number of selected component:
cmdline: /usr/bin/python3 -tt /usr/sbin/mock -r fedora-rawhide-x86_64 --rebuild boost-1.59.0-1.fc24.src.rpm
runlevel: N 5
#1 logOutput in /usr/lib/python3.4/site-packages/mockbuild/util.py:361
#2 do in /usr/lib/python3.4/site-packages/mockbuild/util.py:455
#3 trace in /usr/lib/python3.4/site-packages/mockbuild/trace_decorator.py:84
#4 _selinuxDoYum in /usr/lib/python3.4/site-packages/mockbuild/plugins/selinux.py:104
#5 trace in /usr/lib/python3.4/site-packages/mockbuild/trace_decorator.py:84
#6 execute in /usr/lib/python3.4/site-packages/mockbuild/package_manager.py:85
#7 trace in /usr/lib/python3.4/site-packages/mockbuild/trace_decorator.py:84
#8 builddep in /usr/lib/python3.4/site-packages/mockbuild/package_manager.py:105
#9 trace in /usr/lib/python3.4/site-packages/mockbuild/trace_decorator.py:84
#10 builddep in /usr/lib/python3.4/site-packages/mockbuild/package_manager.py:255
Created attachment 1067236 [details]
Created attachment 1067237 [details]
Is there way to reproduce it?
Only way I know it *may* reproduce is to run mock as subprocess, then kill the parent process and then the terminal. Then the child process may produce such traceback.
However it is so obscure to me. How this happened to you?
Ah, I think this one may have happened when I got an X server crash, so the parent and terminal (a konsole window) and everything else would have been killed.
So maybe just close this.
It would be quite hard do fix mock to not produce error in such case (and distinguish it from cases where it is actually error). Since it even happen in some special timing... IMO not worth the work and I would like to focus on other bugs, which are real blockers.