Wireshark mailing list archives
Re: buildbot down?
From: "Maynard, Chris" <Christopher.Maynard () IGT com>
Date: Mon, 10 Apr 2017 18:12:19 +0000
Would taskkill.exe help? For example, "taskkill.exe /im dumpcap.exe" , etc. I've also used WMIC in the past to save ProcessID's of tasks so you can later kill specific instances of a task instead of all of them with the same name. I'd refer you to the dumpcap.bat file posted on https://wiki.wireshark.org/Tools for how I did that. - Chris [1]: https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/taskkill.mspx?mfr=true - Chris
-----Original Message----- From: wireshark-dev-bounces () wireshark org [mailto:wireshark-dev- bounces () wireshark org] On Behalf Of Gerald Combs Sent: Monday, April 10, 2017 2:06 PM To: Developer support list for Wireshark <wireshark-dev () wireshark org> Subject: Re: [Wireshark-dev] buildbot down? On 4/9/17 1:23 AM, Graham Bloice wrote:On 9 April 2017 at 01:54, Gerald Combs <gerald () wireshark org <mailto:gerald () wireshark org>> wrote: On 4/8/17 10:47 AM, Peter Wu wrote: > > There is another problem though with the Petri-Dish builder, a previous > build on the Petri-Dish Windows x86 builder failed and left a process on > the machine, breaking all following builds. Gerald, can you have a look? It's back up. > Maybe it is an idea to add a pass that kills all > dumpcap/tshark/wireshark processes before starting the build?(Assuming> that no other builds happen in parallel). Is there a straightforward equivalent to "kill -9 $( lsof -t /path/to/buildbot )" on Windows? Difficult to identify which process you want to kill with Stop-Process. With PS 4.0 and later you can run ((Get-Process -IncludeUserName).where({$_.username -AND $_.username -notmatch "^NT"})) to get the processes owned by the user account running the command, but there's still too many in there that shouldn't be stopped. Maybe Get-Process | Where-Object -Property ProcessName -match ".*(Process1|Process2|Process3).*" | Stop-Process would do if the number of processes to look for isn't too bad.How difficult would it be to parse the output of the Sysinternals "Handle" utility in PS? That would presumably tell us which process has the build directory locked while limiting the risk of clobbering any other Buildbot instances that happen to be running. ________________________________________________________________ ___________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
CONFIDENTIALITY NOTICE: This message is the property of International Game Technology PLC and/or its subsidiaries and may contain proprietary, confidential or trade secret information. This message is intended solely for the use of the addressee. If you are not the intended recipient and have received this message in error, please delete this message from your system. Any unauthorized reading, distribution, copying, or other use of this message or its attachments is strictly prohibited. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- buildbot down? Simon Barber (Apr 07)
- Re: buildbot down? Peter Wu (Apr 08)
- Re: buildbot down? Gerald Combs (Apr 08)
- Re: buildbot down? Graham Bloice (Apr 09)
- Re: buildbot down? Gerald Combs (Apr 10)
- Re: buildbot down? Maynard, Chris (Apr 10)
- Re: buildbot down? Maynard, Chris (Apr 10)
- Re: buildbot down? Graham Bloice (Apr 11)
- Re: buildbot down? Gerald Combs (Apr 13)
- Re: buildbot down? Gerald Combs (Apr 08)
- Re: buildbot down? Peter Wu (Apr 08)