Skip Menu | will be shut down on March 1st, 2021.

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

Report information
The Basics
Id: 100337
Status: stalled
Priority: 0/
Queue: App-cpanminus-reporter

Owner: Nobody in particular
Requestors: ether [...]

Bug Information
Severity: Important
Broken in: 0.11
Fixed in: (no value)

Subject: a failing result for was submitted as a PASS
Download (untitled) / with headers
text/plain 559b
$; cpanm --mirror-only --mirror CPAN; cpanm-reporter CPAN --> Working on CPAN Fetching ... OK Configuring CPAN-2.05 ... OK Building and testing CPAN-2.05 ... FAIL ! Installing CPAN failed. See /Users/ether/.cpanm/work/1415990050.50326/build.log for details. Retry with --force to force install it. sending: (, ANDK, CPAN-2.05, PASS) Attached is the build log.
Subject: build.log
Download build.log
application/octet-stream 18.8k

Message body not shown because it is not plain text.

Download (untitled) / with headers
text/plain 334b
Explicitly referencing this log file resulted in the same thing, so it's definitely parsing this log and not a different one: $; cpanm-reporter --force --build_logfile=/Users/ether/.cpanm/work/1415990050.50326/build.log sending: (, ANDK, CPAN-2.05, PASS)
Download (untitled) / with headers
text/plain 1.1k
Hi! So, this is a real bug in cpanm-reporter, but it's sort of an unsolvable one - at least until we can get it really merged into cpanm. See, the failing report includes a "Result: PASS" line in the middle of the test, and from reading the build.log we can't really tell it apart from an actual "Result: PASS". I have discussed this at length with renormalist and we came to the conclusion that no matter what you try and parse, there could always be a module that would print the string we're parsing and we would not be able to tell it apart from the actual cpanm testing output :( The solution could be any of the following: 1) Merge cpanm-reporter to cpanm so we always fetch the test output and will never have to parse anything anymore. This is being discussed on It is the final goal for cpanm-reporter, but it might need some work to get it going the way we need. 2) Blacklist on the parser all modules that are known to produce bad reports. 3) Special-case on the parser all modules that known to produce bad reports. #1 is of course our main goal, but like I said it might need some work :/ What's our second best option?

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to