From: "Niels Kristian \"Ænkå\" Jensen" <nkj@internetgruppen.dk>
To: cygwin@cygwin.com
Subject: Cygwin-test result (perhaps leaking file descriptors)
Date: Thu, 01 Nov 2018 10:10:00 -0000 [thread overview]
Message-ID: <d9042551080f9a22a8c6f2ba0b978b54@internetgruppen.dk> (raw)
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
reply other threads:[~2018-11-01 10:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d9042551080f9a22a8c6f2ba0b978b54@internetgruppen.dk \
--to=nkj@internetgruppen.dk \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).