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

t/04-nativecall/20-concurrent.t flops #5786

Open
p6rt opened this issue Nov 7, 2016 · 5 comments
Open

t/04-nativecall/20-concurrent.t flops #5786

p6rt opened this issue Nov 7, 2016 · 5 comments
Labels

Comments

@p6rt
Copy link

@p6rt p6rt commented Nov 7, 2016

Migrated from rt.perl.org#130042 (status was 'open')

Searchable as RT130042$

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Nov 7, 2016

From @zoffixznet

The t/04-nativecall/20-concurrent.t included in Rakudo's test suit
appears to be flopping with today's HEAD​: 2016.10-213-ge10f767

I'm disabling this test to quite down travis IRC bot assaults. Please
uncomment the test once the fix is apparent.

To reproduce (error at the end)​:

cpan@​perlbuild2~/CPANPRC/rakudo (nom)$ while ./perl6 --ll-exception
t/04-nativecall/20-concurrent.t; do true; done
1..3
ok 1 - Correct results when running native code across threads
ok 2 - A sleeping native call does not block running/GC in another thread
ok 3 - Can call native function while one in another thread is sleeping
1..3
ok 1 - Correct results when running native code across threads
ok 2 - A sleeping native call does not block running/GC in another thread
ok 3 - Can call native function while one in another thread is sleeping
1..3
ok 1 - Correct results when running native code across threads
ok 2 - A sleeping native call does not block running/GC in another thread
ok 3 - Can call native function while one in another thread is sleeping
1..3
ok 1 - Correct results when running native code across threads
ok 2 - A sleeping native call does not block running/GC in another thread
ok 3 - Can call native function while one in another thread is sleeping
1..3
ok 1 - Correct results when running native code across threads
ok 2 - A sleeping native call does not block running/GC in another thread
ok 3 - Can call native function while one in another thread is sleeping
1..3
Cannot invoke this object (REPR​: P6opaque; Scalar)
at gen/moar/m-CORE.setting​:38278 (././CORE.setting.moarvm​:)
from gen/moar/m-CORE.setting​:38043 (././CORE.setting.moarvm​:)
from gen/moar/m-CORE.setting​:37931 (././CORE.setting.moarvm​:)
from gen/moar/m-CORE.setting​:37945 (././CORE.setting.moarvm​:)
from gen/moar/m-CORE.setting​:37921 (././CORE.setting.moarvm​:)
from gen/moar/m-CORE.setting​:37708 (././CORE.setting.moarvm​:THREAD-ENTRY)

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Nov 10, 2016

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Nov 10, 2016

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

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Nov 19, 2016

From @zoffixznet

Based on AppVeyor, this test still flops, but only on Windows​: https://ci.appveyor.com/project/moritz/rakudo/build/1.0.1552/job/3009q95at2axp4i7

I'm re-fudging the test and re-opening this ticket.

On Thu, 10 Nov 2016 05​:09​:35 -0800, cpan@​zoffix.com wrote​:

This is fixed in
rakudo/rakudo@84eaff4
rakudo/rakudo@0134132
rakudo/rakudo@49fd825

@p6rt

This comment has been minimized.

Copy link
Author

@p6rt p6rt commented Nov 19, 2016

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

@p6rt p6rt added the conc label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.