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
S06-advanced/wrap.t in 6.c-errata roast branch fails a test #5332
Comments
From @hoelzroHere's what the failure looks like:
The failure was introduced by e239f6e. For some reason, changing subtest to a multi sub affects how throws-like evaluates strings, and somehow it affects how the dispatcher is set up for nextsame. |
From @hoelzroI have a fix in place, but it's not a permanent solution. I'd like to get the bottom of the true cause. On 2016-05-20 17:57:53, rob@hoelz.ro wrote:
|
From @zoffixznetIt's just a bad test that relies too much on the internal implementation of subtest(). The explanation is here (esp. last few lines with jnthn++'s explanation): |
The RT System itself - Status changed from 'new' to 'open' |
From @cokeOn Tue Jun 14 19:51:08 2016, cpan@zoffix.com wrote:
So can we close this RT? -- |
From @zoffixznetOn Tue Aug 23 11:57:08 2016, coke wrote:
After we revert hoelzro's temporary fix (that uses a series of `if/else` in one `sub subtest` in lieu of multi-dispatch) and replicate the fix for the bogus test that's currently in master back in 6.c-errata [or use a better test; I forget whether the use of `subtest` was even needed in that test]. I marked my calendar and will take care of all this on Sept. 10th, unless someone beats me to it. |
From @zoffixznetTest fixed in Raku/roast@ab521517a4 Temporary fix reverted in rakudo/rakudo@547fc5154c |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#128203 (status was 'resolved')
Searchable as RT128203$
The text was updated successfully, but these errors were encountered: