Skip to content
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

.splice broken in Rakudo #5486

Closed
p6rt opened this issue Jul 26, 2016 · 7 comments
Closed

.splice broken in Rakudo #5486

p6rt opened this issue Jul 26, 2016 · 7 comments

Comments

@p6rt
Copy link

@p6rt p6rt commented Jul 26, 2016

Migrated from rt.perl.org#128736 (status was 'resolved')

Searchable as RT128736$

@p6rt
Copy link
Author

@p6rt p6rt commented Jul 26, 2016

From @masak

* masak learns that TravisCI has been reporting test failures for 007
since 2016-07-10
<masak> seems something changed in Rakudo around that time
<masak> `This type (Scalar) does not support positional operations` --
does this failure sound familiar to anyone?
<masak> ok, minimiz'd
<masak> m​: my @​a; @​a.splice(0, 0, 42); say @​a
<camelia> rakudo-moar 041919​: OUTPUT<<This type (Scalar) does not
support positional operations[...]>>
* masak submits rakudobug
<masak> bisectable​: my @​a; @​a.splice(0, 0, 42); say @​a
<bisectable> masak​: bisect log​:
https://gist.github.com/1beea81fc4c0f7c56d672e0b3330b44d
<bisectable> masak​: (2016-07-08) rakudo/rakudo@58c2628
<moritz> bisectable++ AlexDaniel++

@p6rt
Copy link
Author

@p6rt p6rt commented Jul 26, 2016

From @masak

<masak> now rebuilding with 58c2628 reverted, and re-spectesting.
<masak> what -- it doesn't even build
<masak> fails during Stage optimize with "This type (Scalar) does not support associative operations"
<masak> I tried realcleaning and re-configuring. same result.
* masak tries `git clean -xdf` too
<masak> ...still the same error.
* masak tries building from 58c2628^
<masak> ...that works.
<masak> interesting. so we're in a situation where we know which commit is faulty, the commit reverts without conflict, but the build is broken after the revert.
* masak reports all this to RT

@p6rt
Copy link
Author

@p6rt p6rt commented Jul 28, 2016

From @lizmat

Fixed (at least temporarily) with cc212cebf80fd37d5 , tests needed

On 26 Jul 2016, at 09​:05, Carl Mäsak (via RT) <perl6-bugs-followup@​perl.org> wrote​:

# New Ticket Created by "Carl Mäsak"
# Please include the string​: [perl #​128736]
# in the subject line of all future correspondence about this issue.
# <URL​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=128736 >

* masak learns that TravisCI has been reporting test failures for 007
since 2016-07-10
<masak> seems something changed in Rakudo around that time
<masak> `This type (Scalar) does not support positional operations` --
does this failure sound familiar to anyone?
<masak> ok, minimiz'd
<masak> m​: my @​a; @​a.splice(0, 0, 42); say @​a
<camelia> rakudo-moar 041919​: OUTPUT<<This type (Scalar) does not
support positional operations[...]>>
* masak submits rakudobug
<masak> bisectable​: my @​a; @​a.splice(0, 0, 42); say @​a
<bisectable> masak​: bisect log​:
https://gist.github.com/1beea81fc4c0f7c56d672e0b3330b44d
<bisectable> masak​: (2016-07-08) rakudo/rakudo@58c2628
<moritz> bisectable++ AlexDaniel++

@p6rt
Copy link
Author

@p6rt p6rt commented Jul 28, 2016

The RT System itself - Status changed from 'new' to 'open'

@p6rt
Copy link
Author

@p6rt p6rt commented Aug 13, 2016

From @masak

<masak> lizmat​: got some bad news -- splice is broken in 007 again
<masak> m​: my @​a; @​a.splice(0, 0, "x"); say +@​a
<camelia> rakudo-moar e89721​: OUTPUT<<0NL>>
<masak> m​: my @​a; @​a.splice(0, 0, "x"); @​a.splice(1, 0, "y")
<camelia> rakudo-moar e89721​: OUTPUT<<Offset argument to splice out of range. Is​: 1, should be in 0..0NL [...]
<masak> lizmat​: ^
* masak submits rakudobug
<masak> heck, let's re-open RT #​128736
<masak> oh, it wasn't closed, it was needstest

@p6rt
Copy link
Author

@p6rt p6rt commented Sep 2, 2016

From @zoffixznet

Tests added in Raku/roast@991398bb7f

@p6rt
Copy link
Author

@p6rt p6rt commented Sep 2, 2016

@zoffixznet - Status changed from 'open' to 'resolved'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant