[issue10826] pass_fds sometimes fails

Antoine Pitrou added the comment: Committed in r88484 (3.x), r88485 (3.2). -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue10826] pass_fds sometimes fails

Gregory P. Smith added the comment: Your patch makes sense to me. I'll commit it after the 3.2 release for 3.2.1. The elease manager can feel free to commit it earlier if it is bothering an important buildbot. -- assignee: -> gregory.p.smith ___

[issue10826] pass_fds sometimes fails

Antoine Pitrou added the comment: Here is a patch to ignore door files when running the fd_status script. It seems to eradicate the intermittent failures on the solaris buildbots. -- keywords: +patch Added file: http://bugs.python.org/file20600/spdoors.patch __

[issue10826] pass_fds sometimes fails

Antoine Pitrou added the comment: > 'D' denotes a door file. There are several of them in the system; the > following ones (from /var/run) match the time stamp: Thanks for the explanation! > It's common for library routines to open a door and keep it open for > the entire process lifetime. >

[issue10826] pass_fds sometimes fails

Martin v. Löwis added the comment: 'D' denotes a door file. There are several of them in the system; the following ones (from /var/run) match the time stamp: Dr--r--r-- 1 daemon daemon 0 Mar 27 2010 kcfd_door Dr--r--r-- 1 root root 0 Mar 27 2010 name_service_door

[issue10826] pass_fds sometimes fails

Antoine Pitrou added the comment: I managed to get further debug info from the OpenIndiana buildbot: -- maxfd = 65536 -- fds that should have been closed: {5, 6, 7, 8, 9, 10, 11, 12, 13} -- fds that remained open: {0, 1, 2, 3, 5} -- debug info: 0 2 posix.stat_result(st_mode=4096, st_ino=380

[issue10826] pass_fds sometimes fails

Antoine Pitrou added the comment: So, I added some debug info to test_pass_fds: -- fds that should have been closed: {5, 6, 7, 8, 9, 10, 11, 12, 13} -- fds that remained open: {0, 1, 2, 3, 5} -- debug info: 0 8194 posix.stat_result(st_mode=8592, st_ino=12582920, st_dev=82051072, st_nlink=1,

[issue10826] pass_fds sometimes fails

Antoine Pitrou added the comment: Happened also on the OpenIndiana buildbot: http://www.python.org/dev/buildbot/all/builders/x86%20OpenIndiana%203.x/builds/492/steps/test/logs/stdio -- ___ Python tracker

[issue10826] pass_fds sometimes fails

Antoine Pitrou added the comment: Another (perhaps more likely) possibility is that fd 5 was properly closed, but another one created at startup by the child Python interpreter. How could we diagnose that? -- ___ Python tracker

[issue10826] pass_fds sometimes fails

New submission from Antoine Pitrou : This happens selectively (and intermittently) on the Solaris buildbot: test_pass_fds (test.test_subprocess.POSIXProcessTestCase) ... -- maxfd = 256 [36787 refs] -- fds that should have been closed: {5, 6, 7, 8, 9, 10, 11, 12, 13} -- fds that remained open: