This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Cygwin-test result (perhaps leaking file descriptors)
- From: Niels Kristian "Ænkå" Jensen <nkj at internetgruppen dot dk>
- To: cygwin at cygwin dot com
- Date: Thu, 01 Nov 2018 11:09:56 +0100
- Subject: Cygwin-test result (perhaps leaking file descriptors)
Hi all,
I've updated cygwin1.dll to
https://cygwin.com/snapshots/x86/cygwin1-20181029.dll.xz before running
this test:
09:20:00 Started by timer
09:20:00 [EnvInject] - Loading node environment variables.
09:20:00 Building remotely on NKJ-Win10 (WIN64) in workspace
d:\jenkins-slave-dtdkcphpw200063-1\workspace\Misc\Count-synergy-locks
09:20:00 [Count-synergy-locks] $ sh -xe
C:\cygwin\tmp\jenkins6589319230840350781.sh
09:20:01 Cygwin wrapper for Jenkins (C:\cygwin\sh.exe v1)
09:20:01 ++ ccm monitor --showlocks
09:20:01 ++ wc -l
09:20:01 + OUTPUT=169
09:20:01 + echo 169
09:20:01 169
09:20:01 + sleep 169
09:22:25 Process leaked file descriptors. See
https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors
for more information
09:22:25 Build step 'Execute shell' marked build as failure
09:22:26 [BFA] Scanning build for known causes...
09:22:26 [BFA] No failure causes found
09:22:26 [BFA] Done. 0s
09:22:26 Finished: FAILURE
It only happened once out of >50 tests. I see no reason for "sleep" to
leak file descriptors?
Now I'll run some more tests to check if it happens again. If you need a
test case, this could be a candidate.
BTW, the troubleshooting link is outdated. The Jenkins "leak"
description is here now:
https://wiki.jenkins.io/display/JENKINS/Spawning+processes+from+build
Best regards,
Niels Kristian Jensen
------------------------------------------
Spejd er sejt!
Det Danske Spejderkorps
------------------------------------------
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple