|Summary:||test for FD_CLOEXEC seems to be unreliable on NetBSD|
|Product:||dbus||Reporter:||Simon McVittie <smcv>|
|Component:||core||Assignee:||D-Bus Maintainers <dbus>|
|Status:||RESOLVED FIXED||QA Contact:||D-Bus Maintainers <dbus>|
|Priority:||low||CC:||jmmv, msniko14, prlw1|
|i915 platform:||i915 features:|
Description Simon McVittie 2014-09-15 17:15:15 UTC
Comment 1 Simon McVittie 2014-09-16 11:15:51 UTC
From the thread starting here http://mail-index.netbsd.org/tech-kern/2014/09/15/msg017660.html it seems that the problem is that we're inheriting miscellaneous fds from the environment, which are not close-on-exec. So the D-Bus test framework, intended to make sure that D-Bus starts its activated services with only stdin, stdout and stderr open, has found bugs in NetBSD's GUI environment where it starts applications with more than stdin, stdout and stderr open. One possible solution would be to iterate through fds >= 3 during test startup and make them all close-on-exec, so that only the new fds opened by libdbus are subject to this check. (This is hard to do portably, but doing the same thing as that check would be "good enough".) Another would be to fix your GUI, or run these tests in a non-GUI environment.
Comment 2 Simon McVittie 2014-10-24 12:49:43 UTC
Attachment #108352 [details] over on Bug #73689 should fix this.
Comment 3 Ralf Habacker 2014-10-25 08:31:54 UTC
fixed with bug #73689