Ticket #1568 (closed bug: fixed)

Opened 12 years ago

Last modified 12 years ago

`make smoke` reports a timeout error

Reported by: brianwisti Owned by:
Priority: normal Milestone: 2.4
Component: testing Version:
Severity: medium Keywords:
Cc: Language:
Patch status: applied Platform: darwin

Description

I'm seeing timeout issues running make smoke today that I didn't when I last built Parrot a few months ago:

  • $perl Configure.pl # checked Perl 5.10.1 and 5.12
  • make
  • make test
  • make smoke
...
All tests successful.
Files=348, Tests=12468, 98 wallclock secs ( 2.22 usr  1.18 sys + 48.27 cusr 22.63 csys = 74.30 CPU)
Result: PASS

TAP Archive created at /Users/brian/src/parrot-2.3.0/parrot_test_run.tar.gz
Could not upload report to Smolder at http://smolder.plusthree.com  
HTTP CODE: 500 (read timeout)
make: *** [smolder_test] Error 255

The actual smoke test report appears to be  here.

I'm able to duplicate the behavior using Perl 5.10 and 5.12, building smoke reports for Parrot 2.0 and 2.3. I will attach the output of perl5.10.1 -V in case it is relevant, and not just a temporary network hiccup.

Attachments

perl-info.txt Download (2.2 KB) - added by brianwisti 12 years ago.
smoke_extend_timeout.patch Download (425 bytes) - added by brianwisti 12 years ago.

Change History

Changed 12 years ago by brianwisti

  Changed 12 years ago by rurban

Thanks. Smolder is not reacting fast enough. Try from the docs to upload again:

perl -Ilib -MParrot::Harness::Smoke -e'Parrot::Harness::Smoke::send_archive_to_smolder(Parrot::Harness::Smoke::collect_test_environment_data())'

follow-up: ↓ 4   Changed 12 years ago by brianwisti

Running perl -Ilib -MParrot::Harness::Smoke -e'Parrot::Harness::Smoke::send_archive_to_smolder(Parrot::Harness::Smoke::collect_test_environment_data())' produces the same output.

The reports are being uploaded successfully, but the $ua timeout makes it look like a complete failure. The error message (specified in lib/Parrot/Harness/Smoke.pm:150) is confusing in this case. I see many entries in the recent smoke reports page which appear to be from me, but the timeout from Smolder is treated like a complete failure.

If I increase the timeout, Smolder has enough time to send back a report ID.

# lib/Parrot/Harness/Smoke.pm:118
my $ua = LWP::UserAgent->new();
$ua->timeout(360);
$ua->agent( 'Parrot::Harness::Smoke' );
$ua->env_proxy();
$ make smoke
...
All tests successful.
Files=348, Tests=12468, 94 wallclock secs ( 2.21 usr  1.25 sys + 48.79 cusr 22.39 csys = 74.64 CPU)
Result: PASS

TAP Archive created at /Users/brian/src/svn-parrot/parrot/parrot_test_run.tar.gz
Test report successfully sent to Smolder at
http://smolder.plusthree.com/app/projects/report_details/33341
You can see other recent reports at
http://smolder.plusthree.com/app/projects/smoke_reports/8 .

  Changed 12 years ago by gerd

  • milestone changed from 2.3 to 2.4

in reply to: ↑ 2 ; follow-up: ↓ 5   Changed 12 years ago by jkeenan

Replying to brianwisti:

The reports are being uploaded successfully, but the $ua timeout makes it look like a complete failure. The error message (specified in lib/Parrot/Harness/Smoke.pm:150) is confusing in this case. I see many entries in the recent smoke reports page which appear to be from me, but the timeout from Smolder is treated like a complete failure. If I increase the timeout, Smolder has enough time to send back a report ID. {{{ # lib/Parrot/Harness/Smoke.pm:118 my $ua = LWP::UserAgent->new(); $ua->timeout(360); $ua->agent( 'Parrot::Harness::Smoke' ); $ua->env_proxy(); }}}

This is a problem of long-standing and for the most part is out of our control, as our Smolder services are donated to us.

However, I think your workaround deserves attention. Could you please attach it to this ticket in the form of a patch?

Thank you very much.

kid51

Changed 12 years ago by brianwisti

in reply to: ↑ 4   Changed 12 years ago by brianwisti

Replying to jkeenan:

This is a problem of long-standing and for the most part is out of our control, as our Smolder services are donated to us. However, I think your workaround deserves attention. Could you please attach it to this ticket in the form of a patch?

Done more or less according to directions mentioned at  http://trac.parrot.org/parrot/wiki/NewParrotDeveloperGuide - please let me know if I need to use different command line options or anything else.

Thanks!

Brian

  Changed 12 years ago by dukeleto

  • status changed from new to closed
  • resolution set to fixed
  • patch set to applied
Note: See TracTickets for help on using tickets.