On Mon, Jun 25, 2012 at 5:21 PM, Bopolissimus X Platypus <[email protected]> wrote: > When a job running on the slave is aborted (either at the browser via > jenkins job control UI) or by the build timeout plugin, some commands > started by batch files don't exit (they keep running).
this bug report: https://issues.jenkins-ci.org/browse/JENKINS-6188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel describes what I'm seeing. I'm running on: Jenkins 1.462 (started manually, java -jar jenkins.war) Windows Server 2003. Gerald -- Gerald Timothy Quimpo bopolissimus_at_gmail.com http://bopolissimus.*b*l*o*g*s*p*o*t*.com "(Postgresql) Cursors are biased towards fast-start plans on the theory that you may not be intending to fetch the whole result. Queries with ORDER BY and/or LIMIT are particularly likely to see plan changes as a consequence of that."
