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

9515bb7636d2352a68bf770d80964f5907526fbc broke rakudo.parrot #3464

Closed
p6rt opened this issue Jul 29, 2014 · 3 comments
Closed

9515bb7636d2352a68bf770d80964f5907526fbc broke rakudo.parrot #3464

p6rt opened this issue Jul 29, 2014 · 3 comments

Comments

@p6rt
Copy link

p6rt commented Jul 29, 2014

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

Searchable as RT122436$

@p6rt
Copy link
Author

p6rt commented Jul 29, 2014

From @coke

last 2 days we've started seeing thousands of failures on the daily
rakudo.parrot run. Doing a git bisect, looks like the commit that
started the failures is​:

$ git bisect good
9515bb7636d2352a68bf770d80964f5907526fbc is the first bad commit
commit 9515bb7636d2352a68bf770d80964f5907526fbc
Author​: jnthn <jnthn@​jnthn.net>
Date​: Sun Jul 27 22​:22​:59 2014 +0200

  Tweak some protos for better Junction failover.

  We can make the proto itself be (Any, Any), meaning it fails to bind.
  However, this also means that the multi-dispatcher never gets chance
  to sneak an entry into the cache for the Junction case, so we have to
  go through the slow-path binder to fail over every time, rather than
  cheaply identifying we should hit the Junction dispatcher.

... whether or not my git bisect is right, here's a golf of one of the
currently aborting spectests​:

19​:10 < [Coke]> r​: use Test; is(​:10('01110') , 0d1110, "​:10('01110') is default
  decimal");
19​:10 <+camelia> rakudo-{jvm,moar} c00999​: OUTPUT«ok 1 - :10('01110') is default
  decimal␤»
19​:10 <+camelia> ..rakudo-parrot c00999​: OUTPUT«(signal )»

--
Will "Coke" Coleda

@p6rt
Copy link
Author

p6rt commented Aug 19, 2014

From @coke

On Tue Jul 29 16​:12​:12 2014, coke wrote​:

last 2 days we've started seeing thousands of failures on the daily
rakudo.parrot run. Doing a git bisect, looks like the commit that
started the failures is​:

$ git bisect good
9515bb7636d2352a68bf770d80964f5907526fbc is the first bad commit
commit 9515bb7636d2352a68bf770d80964f5907526fbc
Author​: jnthn <jnthn@​jnthn.net>
Date​: Sun Jul 27 22​:22​:59 2014 +0200

Tweak some protos for better Junction failover.

We can make the proto itself be (Any, Any), meaning it fails to bind.
However, this also means that the multi-dispatcher never gets chance
to sneak an entry into the cache for the Junction case, so we have to
go through the slow-path binder to fail over every time, rather than
cheaply identifying we should hit the Junction dispatcher.

... whether or not my git bisect is right, here's a golf of one of the
currently aborting spectests​:

19​:10 < [Coke]> r​: use Test; is(​:10('01110') , 0d1110, "​:10('01110')
is default
decimal");
19​:10 <+camelia> rakudo-{jvm,moar} c00999​: OUTPUT«ok 1 - :10('01110')
is default
decimal␤»
19​:10 <+camelia> ..rakudo-parrot c00999​: OUTPUT«(signal )»

The commit that caused this was re-worked to avoid the issue. Closing ticket.

--
Will "Coke" Coleda

@p6rt p6rt closed this as completed Aug 19, 2014
@p6rt
Copy link
Author

p6rt commented Aug 19, 2014

@coke - Status changed from 'new' to 'resolved'

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

No branches or pull requests

1 participant