#2176: buildslave hangs trying to kill process after "1200 seconds without
output"
--------------------+--------------------
Reporter: hjwp | Owner:
Type: defect | Status: new
Priority: major | Milestone: 0.8.+
Version: 0.8.5 | Resolution:
Keywords: windows |
--------------------+--------------------
Comment (by callek):
Not sure what you mean by "anything special", but in some cases, we
forcibly kill chrome, firefox and chromedriver because sometimes they stay
running and then buildbot doesn't recognise that the test run has
finished.
----
Well chrome and Firefox both do "something special", for my purposes of
the question. Firefox generally restarts its process, (which can cause
buildbot to lose track of the actual process you spawned, since the
spawned pid !== the firefox.exe pid after a few seconds of startup)
Chrome does a thing called "Job Objects" with spawned processes, (and I am
not sure if they restart a main process similar to how Firefox does), but
my quick-and-dirty pre-existing solution that would work for Firefox won't
work if you are using chrome (or any program that uses windows "Job
Objects".
I have plans to *try* and tackle this windows-specific issue at some point
in the next few months though....
But glad to hear you did get a solution working for you.
--
Ticket URL: <http://trac.buildbot.net/ticket/2176#comment:6>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
