Bug #89903 for Crypt-MagicSignatures-Key: tests run too long

Wed Oct 30 14:00:20 2013 victor [...] vsespb.ru - Ticket created

Subject:

tests run too long

it was running more than 10 mins, so I terminated the process: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 28428 perltest 20 0 39660 12m 2396 R 99.9 0.6 10:14.11 perl perltest 28428 99.7 0.6 39660 13284 ? R 20:36 10:31 /home/perltest/perl5/perlbrew/perls/perl-5.16.3-thread-multi/bin/perl -w t/12-key-gen.t here is smoke report (which is failure, because I manually terminated the process) http://www.cpantesters.org/cpan/report/d45d9300-382c-11e3-9fcf-edbcf642ae7c I tried to run tests manually, and I've got: Files=12, Tests=137, 682 wallclock secs ( 0.26 usr 0.19 sys + 657.36 cusr 22.14 csys = 679.95 CPU) Files=12, Tests=137, 263 wallclock secs ( 0.14 usr 0.21 sys + 246.60 cusr 12.58 csys = 259.53 CPU) Files=12, Tests=137, 681 wallclock secs ( 0.29 usr 0.25 sys + 649.82 cusr 25.66 csys = 676.02 CPU) Files=12, Tests=137, 1461 wallclock secs ( 0.03 usr 0.16 sys + 1402.61 cusr 48.70 csys = 1451.50 CPU i.e. from 263 to 1461 seconds. unpredicible time. Note that I am running VPS server, so cannot be sure 100% that this time difference not caused by underlying hardware load.

Mon Nov 04 12:41:58 2013 AKRON [...] cpan.org - Correspondence added

Thanks for your report! I agree that 10 minutes is not acceptable (or is at least impolite) for a test suite, so I skipped the test in case the Math::Prime::Util::GMP module is not installed (just uploaded v0.10). Key generation can take a varying time due to random prime number generation, so this can not be considered a bug. Thank you very much! Nils On Wed Oct 30 14:00:20 2013, vsespb wrote: Show quoted text

> it was running more than 10 mins, so I terminated the process: > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 28428 perltest 20 0 39660 12m 2396 R 99.9 0.6 10:14.11 perl > > perltest 28428 99.7 0.6 39660 13284 ? R 20:36 10:31 > /home/perltest/perl5/perlbrew/perls/perl-5.16.3-thread-multi/bin/perl > -w t/12-key-gen.t > > here is smoke report (which is failure, because I manually terminated > the process) http://www.cpantesters.org/cpan/report/d45d9300-382c- > 11e3-9fcf-edbcf642ae7c > > I tried to run tests manually, and I've got: > > Files=12, Tests=137, 682 wallclock secs ( 0.26 usr 0.19 sys + 657.36 > cusr 22.14 csys = 679.95 CPU) > Files=12, Tests=137, 263 wallclock secs ( 0.14 usr 0.21 sys + 246.60 > cusr 12.58 csys = 259.53 CPU) > Files=12, Tests=137, 681 wallclock secs ( 0.29 usr 0.25 sys + 649.82 > cusr 25.66 csys = 676.02 CPU) > Files=12, Tests=137, 1461 wallclock secs ( 0.03 usr 0.16 sys + > 1402.61 cusr 48.70 csys = 1451.50 CPU > > i.e. from 263 to 1461 seconds. unpredicible time. Note that I am > running VPS server, so cannot be sure 100% that this time difference > not caused by underlying hardware load.

Mon Nov 04 12:41:59 2013 The RT System itself - Status changed from 'new' to 'open'

Mon Nov 04 12:41:59 2013 AKRON [...] cpan.org - Status changed from 'open' to 'resolved'

Mon Nov 04 12:41:59 2013 AKRON [...] cpan.org - Taken

Wed Nov 06 08:32:40 2013 AKRON [...] cpan.org - Correspondence added

Hopefull fixed in v0.10. Am Mo 04. Nov 2013, 12:41:58, AKRON schrieb: Show quoted text

> Thanks for your report! I agree that 10 minutes is not acceptable (or > is at least impolite) for a test suite, so I skipped the test in case > the Math::Prime::Util::GMP module is not installed (just uploaded > v0.10). > > Key generation can take a varying time due to random prime number > generation, so this can not be considered a bug. > > Thank you very much! > Nils > > > On Wed Oct 30 14:00:20 2013, vsespb wrote:

> > it was running more than 10 mins, so I terminated the process: > > > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > > 28428 perltest 20 0 39660 12m 2396 R 99.9 0.6 10:14.11 perl > > > > perltest 28428 99.7 0.6 39660 13284 ? R 20:36 10:31 > > /home/perltest/perl5/perlbrew/perls/perl-5.16.3-thread-multi/bin/perl > > -w t/12-key-gen.t > > > > here is smoke report (which is failure, because I manually terminated > > the process) http://www.cpantesters.org/cpan/report/d45d9300-382c- > > 11e3-9fcf-edbcf642ae7c > > > > I tried to run tests manually, and I've got: > > > > Files=12, Tests=137, 682 wallclock secs ( 0.26 usr 0.19 sys + 657.36 > > cusr 22.14 csys = 679.95 CPU) > > Files=12, Tests=137, 263 wallclock secs ( 0.14 usr 0.21 sys + 246.60 > > cusr 12.58 csys = 259.53 CPU) > > Files=12, Tests=137, 681 wallclock secs ( 0.29 usr 0.25 sys + 649.82 > > cusr 25.66 csys = 676.02 CPU) > > Files=12, Tests=137, 1461 wallclock secs ( 0.03 usr 0.16 sys + > > 1402.61 cusr 48.70 csys = 1451.50 CPU > > > > i.e. from 263 to 1461 seconds. unpredicible time. Note that I am > > running VPS server, so cannot be sure 100% that this time difference > > not caused by underlying hardware load.

Wed Nov 06 08:32:41 2013 AKRON [...] cpan.org - Fixed in 0.10 added