develooper Front page | perl.perl5.porters | Postings from December 2014

Re: more smoker constipation?

Thread Previous | Thread Next
George Greer
December 5, 2014 15:45
Re: more smoker constipation?
Message ID:
On Fri, 5 Dec 2014, Dave Mitchell wrote:

> Hi George, some of your smoke-me smokers seem to be stuck again.
> Based on what I see under,
> it seems that:
> linux
>    smoke-me_clang/                          no candidates; doesn't seem
>                                             to have smoked for a long time
>    smoke-me_clang_quick/                    no candidates; doesn't seem
>                                             to have smoked for a long time

I turned these off since they were essentially duplicating the g++ runs.
They were replaced by the equivalent plus "sanitize=address" version.  I 
should go delete those directories now to avoid confusion.  I made a post 
about the changes to p5p a few months back but it was in reply to a thread 
so it may not have been as visisble as it should.

>    smoke-me_clang_quick_sanitize=address/   seems ok
>    smoke-me_clang_quick_sanitize=undefined/ no candidates; doesn't seem
>                                             to have smoked for a long time

Perl isn't "sanitize=undefined" clean so it would always fail.  I suppose 
I could turn it on but not Cc: p5p, which would be useful.  I'll do that 

>    smoke-me_clang_sanitize=address/         active; I'm 3rd in queue; 1st
>                                             is from 27 nov; but last
>                                             finished seems to be 26 nov;
>                                             stuck???
>    smoke-me_g++/                            active; I'm being smoked;
>                                             last finished seems to be 5
>                                             dec; ok?
>    smoke-me_g++_quick/                      seems ok

The 'smoke-me_clang_sanitize=address' is really slow but shouldn't be 
THAT slow. I'll check it tonight.

> win32
>    smoke-me/                                supposedly its been smoking
>                                             jhi/maint-5.20-necromantic
>                                             since 29 Nov; last finished
>                                             smoke was on 29 Nov; stuck???

A power outage made the VM blue screen with inaccessible boot device when 
it tries to start now.  I'll fix it this weekend.  Should just involve 
booting off the (virtual) installation CD and running chkdsk on the drive.

George Greer

Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About