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

Re: status of smoke-me testing

Thread Previous | Thread Next
Tony Cook
May 30, 2021 11:13
Re: status of smoke-me testing
Message ID:
On Sat, May 29, 2021 at 10:08:18PM -0400, James E Keenan wrote:
> On 5/29/21 8:05 PM, Ricardo Signes wrote:
> > I was looking at
> > <> 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, 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.

Unless it's changed, when Test::Smoke makes one attempt to send a
report by http(s), and if that fails no further attempts are made.

> And many fewer testers are sending reports.  Go to TonyC's aggregator,
>  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. *is* picking up reports transmitted via
> HTTP::Tiny, but I don't know whether it is picking up reports transmitted
> via email.

My aggregator had fetching disabled because it was only
failing (and sending me failure messages)

It still seems to be only failing, I tried loading both the API
endpoint and the home page a few times and got 502s each time.

I've set it to fetch daily, maybe we'll get lucky. only receives message sent via HTTP::Tiny.

> 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* and
>  Now they *only* appear on

It used to be the default, and if it's useful, the appropriate parts from
my old smokecurrent_config are:

          'mail' => '1',
          'mail_type' => 'MIME::Lite',
          'mserver' => 'localhost',
          'from' => '',
          'to' => '',

Mail is going to remain the fastest way to get reports into - I'm subscribed to the daily-build-reports list
and a procmail rule pushes the message to as
soon as I receive it[1][2], while I have to poll for for

> Also, the "new" 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. is also a VM (at Linode Sydney).

I have no control over

I've considered offering to host it (on the same Linode), but IIRC it
needed occasional restarts even when it was hosted at booking.


[1] with retries
[2] I also check daily for any missing reports.

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