Summary: | =sys-apps/portage-2.1.11.22: failes test portage.tests.ebuild.test_ipc_daemon.IpcDaemonTestCase | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Toralf Förster <toralf> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | Normal | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=437180 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 431026 | ||
Attachments: | build log |
Description
Toralf Förster
2012-09-26 17:48:21 UTC
It works for me. Can you reproduce it? I'll paste the failure from your log here so that it's visible without downloading and extracting the log: FAIL: testIpcDaemon (portage.tests.ebuild.test_ipc_daemon.IpcDaemonTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "/var/tmp/portage/sys-apps/portage-2.1.11.22/work/portage-2.1.11.22/pym/portage/tests/__init__.py", line 190, in run testMethod() File "/var/tmp/portage/sys-apps/portage-2.1.11.22/work/portage-2.1.11.22/pym/portage/tests/ebuild/test_ipc_daemon.py", line 130, in testIpcDaemon self.assertEqual(proc.returncode == os.EX_OK, False) AssertionError: True != False It's possible that the test could fail due to your system being heavily loaded, and this should fix it: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=c371cb4d1a1858c6271af9abee53b1dcc28d5435 (In reply to comment #2) > It's possible that the test could fail due to your system being heavily > loaded, and this should fix it: > yep - that was the case - now 2 times in a row the test passes fine (In reply to comment #2) > It's possible that the test could fail due to your system being heavily > loaded, and this should fix it: FWIW an "ebuild ... test" works fine, wheres "emerge ..." let this test fails due to PORTAGE_NICENESS="3" which lowers the CPU freq on my i5 to 800 MHz. This is fixed in 2.1.11.23 and 2.2.0_alpha134. |