Skip Menu |

This queue is for tickets about the App-cpanminus-reporter CPAN distribution.

Report information
The Basics
Id: 102995
Status: resolved
Priority: 0/
Queue: App-cpanminus-reporter

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 0.12
Fixed in: (no value)



Subject: Perl version mismatch in reports
This report: http://www.cpantesters.org/cpan/report/0c49c36e-c29d-11e4-89ad-eddcc615bc7f is attributed to perl 5.21.9, but there is evidence that the build was really done for perl 5.20.1. I don't know if this is a pilot error, or inherent problem of App-cpanminus-reporter.
On 2015-03-22 06:04:26, SREZIC wrote: Show quoted text
> This report: > http://www.cpantesters.org/cpan/report/0c49c36e-c29d-11e4-89ad- > eddcc615bc7f > is attributed to perl 5.21.9, but there is evidence that the build was > really done for perl 5.20.1. I don't know if this is a pilot error, or > inherent problem of App-cpanminus-reporter.
There is a documentation warning that 'cpanm-reporter' must be run immediately after, and using the same perl and environment as, the module installation itself, but this doesn't seem to be checked in any way. However this doesn't seem to be the problem here, as it's cpanm-reporter itself that does 'perl -V', not the distribution installation, and it's in perl -V that we can see that a different perl was in use than how the report was submitted.
On 2015-03-22 09:04:26, SREZIC wrote: Show quoted text
> This report: > http://www.cpantesters.org/cpan/report/0c49c36e-c29d-11e4-89ad- > eddcc615bc7f > is attributed to perl 5.21.9, but there is evidence that the build was > really done for perl 5.20.1. I don't know if this is a pilot error, or > inherent problem of App-cpanminus-reporter.
Another sample: http://www.cpantesters.org/cpan/report/681049ee-c2a6-11e4-b54b-9b82c615bc7f Here it's rather annoying because http://matrix.cpantesters.org/?dist=Data-Dump-Streamer+2.38 suggests that there are PASS reports for perl 5.21.8 and 5.21.9, but in fact these are only broken test reports.
Oh my... version 0.14 should fix this. I'm sorry it took so long!