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

S17-procasync/basic.t line:80 reason: 'returns Nil (flapping tests)' #4181

Open
p6rt opened this issue May 3, 2015 · 2 comments
Open

S17-procasync/basic.t line:80 reason: 'returns Nil (flapping tests)' #4181

p6rt opened this issue May 3, 2015 · 2 comments
Labels

Comments

@p6rt
Copy link

p6rt commented May 3, 2015

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

Searchable as RT125047$

@p6rt
Copy link
Author

p6rt commented Oct 27, 2016

From @MasterDuke17

================================================================================================
This is Rakudo Perl 6 running in valgrind, a tool for debugging and profiling programs.
Running a program in valgrind usually takes *a lot* more time than running it directly,
so please be patient.
This Rakudo version is 2016.10.74.ga.1.fceeb built on MoarVM version 2016.10.25.geb.46.ed.2,
running on arch (4.7.3.1.arch) / linux (4.7.6.1.ARCH)


==17576== Memcheck, a memory error detector
==17576== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==17576== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==17576== Command​: /home/dan/Source/perl6/install/bin/moar --full-cleanup --execname=./perl6-valgrind-m --libpath=/home/dan/Source/perl6/install/share/nqp/lib --libpath=. /home/dan/Source/perl6/rakudo/perl6.moarvm -e exit
==17576==
==17576==
==17576== HEAP SUMMARY​:
==17576== in use at exit​: 46,740,889 bytes in 191,622 blocks
==17576== total heap usage​: 204,314 allocs, 12,692 frees, 55,094,594 bytes allocated
==17576==
==17576== LEAK SUMMARY​:
==17576== definitely lost​: 8,766 bytes in 181 blocks
==17576== indirectly lost​: 22,368 bytes in 668 blocks
==17576== possibly lost​: 392,896 bytes in 7,019 blocks
==17576== still reachable​: 46,316,859 bytes in 183,754 blocks
==17576== suppressed​: 0 bytes in 0 blocks
==17576== Rerun with --leak-check=full to see details of leaked memory
==17576==
==17576== For counts of detected and suppressed errors, rerun with​: -v
==17576== ERROR SUMMARY​: 0 errors from 0 contexts (suppressed​: 0 from 0)
ok 31 - Proc returned from .start has correct .command
  1..2
  ok 1 - code dies
  ok 2 - right exception type (X​::Multi​::NoMatch)
ok 32 - attempting to create Proc​::Async with wrong arguments throws
==16512==
==16512== Process terminating with default action of signal 6 (SIGABRT)​: dumping core
==16512== at 0x54F004F​: raise (in /usr/lib/libc-2.24.so)
==16512== by 0x54F1479​: abort (in /usr/lib/libc-2.24.so)
==16512== by 0x507BAA6​: uv_mutex_destroy (thread.c​:114)
==16512== by 0x4FFEF61​: gc_free (ConcBlockingQueue.c​:72)
==16512== by 0x4FCC3D4​: MVM_gc_collect_free_nursery_uncopied (collect.c​:580)
==16512== by 0x4FC8E56​: MVM_gc_global_destruction (orchestrate.c​:511)
==16512== by 0x505D531​: MVM_vm_destroy_instance (moar.c​:398)
==16512== by 0x400D2D​: main (main.c​:195)
==16512==
==16512== HEAP SUMMARY​:
==16512== in use at exit​: 130,813,910 bytes in 249,128 blocks
==16512== total heap usage​: 362,165 allocs, 113,037 frees, 182,479,516 bytes allocated
==16512==
==16512== LEAK SUMMARY​:
==16512== definitely lost​: 11,094 bytes in 231 blocks
==16512== indirectly lost​: 22,896 bytes in 670 blocks
==16512== possibly lost​: 394,792 bytes in 7,034 blocks
==16512== still reachable​: 130,385,128 bytes in 241,193 blocks
==16512== suppressed​: 0 bytes in 0 blocks
==16512== Rerun with --leak-check=full to see details of leaked memory
==16512==
==16512== For counts of detected and suppressed errors, rerun with​: -v
==16512== ERROR SUMMARY​: 0 errors from 0 contexts (suppressed​: 0 from 0)

@p6rt
Copy link
Author

p6rt commented Oct 27, 2016

The RT System itself - Status changed from 'new' 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
Labels
Projects
None yet
Development

No branches or pull requests

1 participant