Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 507826 - IOError: [Errno 4] Interrupted system call in locks.py line 175
Summary: IOError: [Errno 4] Interrupted system call in locks.py line 175
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Portage team
URL: https://peps.python.org/pep-0475/
Whiteboard:
Keywords:
Depends on:
Blocks: 910332
  Show dependency tree
 
Reported: 2014-04-16 13:18 UTC by JY
Modified: 2024-07-21 17:19 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
full build log + emerge --info (info.log,27.84 KB, text/x-log)
2014-04-16 13:18 UTC, JY 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description JY 2014-04-16 13:18:15 UTC 
Created attachment 375080 [details]
full build log + emerge --info

With a heavy SMP setup, and parallel-install FEATURES flag, build can randomly fail on any package with IOError: [Errno 4] Interrupted system call error

 * checking 27 files for package collisions
>>> Merging dev-lang/nasm-2.10.07 to /
Traceback (most recent call last):
  File "/usr/lib64/portage/pym/portage/dbapi/_MergeProcess.py", line 234, in _spawn
    prev_mtimes=self.prev_mtimes, counter=counter)
  File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 4839, in merge
    counter=counter)
  File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 4038, in treewalk
    self.vartree.dbapi._fs_lock()
  File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 247, in _fs_lock
    self._fs_lock_obj = lockfile(self._conf_mem_file)
  File "/usr/lib64/portage/pym/portage/locks.py", line 175, in lockfile
    locking_method(myfd, fcntl.LOCK_EX)
IOError: [Errno 4] Interrupted system call


According to doc, syscall interrupted by EINTR should be relaunched, and is not fatal. It simply means that process got a signal while waiting for syscall to complete.
Comment 1 Zac Medico gentoo-dev 2024-07-21 17:19:26 UTC 
This should be fixed since python3.5 by PEP 475 EINTR retry, but we also had an _eintr_func_wrapper that we added for bug 525552 and have since removed.