-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Parsing error, this should not happen, send us a report!" #16
Comments
I locally tweaked the log to have no |
Hey, @kentfredric! Thanks for the report and for all the patience - I know it's been a really long time. Actually, if you fiddle with a distribution, cpanm-reporter should not send a report, right? I mean, it'd be cheating, as the tested version is not the same one as the one on CPAN. We should probably make the parser explicitly test for that and skip those distributions, I'll give it a go eventually, but patches (and general opinions on the subject) are very much welcome! Cheers! |
Possibly. But fixing a target so it works should have little bearing on the reporting of the other things. Personally I think "non-vanilla dists" ( ie: patched by user, however it was patched ) reporting "pass" can be a good thing, but in order for it to be a good thing, it needs to be more obvious in the report that this was done. Then ANDK's analysis can see "X is OK" -> "Why is X working where everyone else failed" -> "X is specially patched" to work. Then its a matter of tracking down an existing bug with said patch, or tracking down the test reporter and asking them what they did. |
This is a tough question, I admit. I tend to believe that the reporter It remains to be suggested that people can add comments to their reports I must reserve the right to change my opinion, things may move in |
Probably related to the fact I chose "look", interactively fixed it by hand, and then exited out and hit 'retry' on cpanm.
The text was updated successfully, but these errors were encountered: