Summary: | sys-apps/portage-2.1.11.24 - testIpcDaemon (portage.tests.ebuild.test_ipc_daemon.IpcDaemonTestCase) ... FAIL | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Jeroen Roovers (RETIRED) <jer> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | zmedico |
Priority: | Normal | Keywords: | InVCS |
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=436334 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 431026 |
Description
Jeroen Roovers (RETIRED)
2012-10-04 14:38:53 UTC
It looks like bug 436334, so apparently the patch in 2.1.11.23 didn't fix it. I wonder if system clock changes by an NTP daemon could trigger this. A possible explanation is that the sleep command is reporting success even after it's been killed by SIGTERM. Hopefully this fixes it: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=e58829dd5e2272b9c3878cd0ec92680fae075b40 Hopefully this is fixed in 2.1.11.25 and 2.2.0_alpha136. I made these additional changes that might affect it: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=e4b64dd7dc7c2217055f110990b2496b71976681 The faulty signal handling can also happen prior to exec. In the case of bug 916566 comment 20, there was a TypeError prior to exec that triggered an unexpected exit status if the SIGTERM didn't arrive first. |