You are aware that you have free access to all of the source code involved, right?
Pick one of the failing tests (like the first one) and run it outside of the "harness" that hides all of the details:
perl -Mblib t/02parse.t 2>&1 | less
Then, if needed, look at the source code in t/02parse.t and figure out why the particular failing test cases are failing. Then, if needed, look at the source code of the module that gets executed for the test and figure out what is causing the failure. Then, if needed, post questions about what you find to try to solicit help diagnosing.
You can even combine the first 3 steps into one session by using the Perl debugger:
perl -d -Mblib t/02parse.t
Me looking at t/02parse.t trying to guess what might possibly cause 343 or its 531 subtests to fail sounds likely to be a particularly inefficient way to try to diagnose your problem.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||