develooper Front page | perl.perl5.porters | Postings from May 2021

Re: status of smoke-me testing

Thread Previous | Thread Next
From:
James E Keenan
Date:
May 30, 2021 02:08
Subject:
Re: status of smoke-me testing
Message ID:
e8c02ddb-4cfc-40b9-94ab-7d849b1688c8@pobox.com
On 5/29/21 8:05 PM, Ricardo Signes wrote:
> I was looking at https://perl5.test-smoke.org/ 
> <https://perl5.test-smoke.org/> earlier today, and looking at some of 
> our branches, and just sort of generally looking around earlier, and I 
> came to wonder:  Is anybody still smoking the smoke-me branches?
> 
> They were useful.  Can someone who has been paying attention the whole 
> time fill me (and us) in as to their status?
> 
> Thanks!
> 

Yes, but it's complicated.

IIRC, perl5.test-smoke.org died last September.  Disk failure.  Many 
years of data lost.  Eventually a replacement was put together, but it's 
not receiving (or, perhaps more precisely, displaying) all the reports 
being generated.

And many fewer testers are sending reports.  Go to TonyC's aggregator, 
http://perl.develop-help.com/.  Note how the overwhelming majority of 
reports are coming from one tester:  Carlos Guevara.  And I believe that 
one consequence of the disk failure last September is that develop-help 
is only picking up reports transmitted via email, that is, sent to some 
perl mailing list.  develop-help is *not* picking up reports that are 
being transmitted via HTTP::Tiny. test-smoke.org *is* picking up reports 
transmitted via HTTP::Tiny, but I don't know whether it is picking up 
reports transmitted via email.

Let me put this concretely.  I have never been able to figure out how to 
send reports via email, so all my reports have been transmitted via 
http.  Up until September, my reports would appear on *both* 
develop-help.com and test-smoke.org.  Now they *only* appear on 
test-smoke.org.

Also, the "new" test-smoke.org is (I have been told) just a VM somewhere 
and is often subject to 504 timeout errors.  The people who maintain 
that have, I believe, time constraints.  Recommend consulting with TonyC 
first, then Tux.

Thank you very much.
Jim Keenan


Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About