Mr. Cantrell,
thanks for the reply. the issue is that if it happens at all for the
smokers; it seems to happen more on windows than other platforms...
for instance Net::Server has been blocking since 2012.
for full details:
https://rt.cpan.org/Ticket/Display.html?id=81993#txn-1395516
---snip from my last RT comment + edits ---
If no skip is put in place; a smoker can not simply modify local code to
include, so exclusion is a remedy but I don't want to do that just yet...
Plus better to start a list of hanging tests and strange behavior than to
ignore it. (it would be nice to get a list of tests/modules that cause
hanging camels...)
I haven't gone so far as to schedule it to run in the background looking
for problematic on my smokers, but i may in the future.
from inside a ps1 script or inside a powershell:
Get-WmiObject Win32_Process -Filter "name = 'perl.exe'" | where
{$_.CommandLine -eq '"C:\strawberry\perl\bin\perl.exe" t/Server_PreFork.t'}
| ForEach-Object { Invoke-WmiMethod -Path $_.__Path –Name Terminate }
Get-WmiObject Win32_Process -Filter "name = 'perl.exe'" | where
{$_.CommandLine -eq '"C:\strawberry\perl\bin\perl.exe"
t/Server_PreForkSimple.t'} | ForEach-Object { Invoke-WmiMethod -Path
$_.__Path –Name Terminate }
this is sorta brute force, but it's quick and works without visually
expanding a process tree and having to discern details.
i'm not sure how to schedule these checks best on the smoker; maybe a
module to hook into the smoking process and perform a task/run a command
every x minutes? idk. anyways for now I've got a quicker resolution. a
solution would be appreciated.
-------
IMHO I think using an automatic timeout is problematic; though I would be
be happy to see something in the smoker to watch for and learn times
associated with test across platforms.
I suppose an automatic timeout that is set high enough takes care of many
issues; but a test could be long running.
cheers to an unstuck tester my polygot friends.
--dave
http://dave.thehorners.com/tech-talk/windows-os/356-powershell-net-control-and-automation
http://perlmonks.org/?node_id=1064341 see the hanging camel.
On Thu, Aug 7, 2014 at 7:51 AM, David Cantrell <da...@cantrell.org.uk>
wrote:
> On Mon, Aug 04, 2014 at 05:18:58PM -0400, Dave Horner wrote:
>
> > Hanging perl process during test of Farabi and others.
> >
> > running cpan from cmd.exe
> > - cpan shell -- CPAN exploration and modules installation (v2.05)
> > cpan> install Farabi
> > ...
> > t/00-compile.t ....... ok
> > t/01-basic.t .........
> > -----------------------------------------
> >
> > The process never returns.
> >
> > Anyways, when smoking and running scripts with perl on windows sometimes
> I
> > come to my unattended automated machine locked and blocking. No fun.
> > I kill the most childish process and it continues; failed.
>
> I find that it happens seldom enough that I can just bounce on C-c.
> People who prefer a bit more automation would presumably have some kind
> of automatic time-out. Here's the bare bones of how to do that in the
> shell. I'm sure you can adapt it to however you're smoking:
>
> #!/bin/bash
>
> function long_running_process() {
> sleep 5
> echo I didn\'t get killed
> }
>
> long_running_process&
> CHILDPID=$!
> sleep 2
> kill $!
>
> $ time ./foo.sh
> real 0m2.008s
> ...
>
> Note the & when long_running_process is invoked, so it's forked off. The
> parent then times out and kills the child before it finishes.
>
> --
> David Cantrell | top google result for "topless karaoke murders"
>
> comparative and superlative explained:
>
> <Huhn> worse, worser, worsest, worsted, wasted
>
