Skip to content

Conversation

@casperisfine
Copy link
Contributor

Otherwise the child will hang forever on exit when trying to dump the profiling data. Which is problematic when trying to profile some programs.

There might be more elegant ways to handle it, this is mostly a proof of concept.

Also it's not quite fully working, the test passes alone, but but if ran after some other specific tests, it end up in a SIGTRAP, which I'm not sure why:

bundle exec rake SEED=26641 TESTOPTS="-v"
...

 1) Failure:
TestVernier#test_that_forked_children_do_not_hang [test/test_vernier.rb:15]:
Expected #<Process::Status: pid 63146 SIGTRAP (signal 5)>
 to be success?.

cc @tenderlove @jhawthorn

Otherwise the child will hang forever on exit when trying to
dump the profiling data. Which is problematic when trying to
profile some programs.

There might be more elegant ways to handle it, this is mostly
a proof of concept.

Also it's not quite fully working, the test passes alone, but
but if ran after some other specific tests, it end up in a
SIGTRAP, which I'm not sure why:

```
bundle exec rake SEED=26641 TESTOPTS="-v"
...

 1) Failure:
TestVernier#test_that_forked_children_do_not_hang [test/test_vernier.rb:15]:
Expected #<Process::Status: pid 63146 SIGTRAP (signal 5)>
 to be success?.

```
@joshuay03 joshuay03 force-pushed the main branch 2 times, most recently from 6f1d6a6 to 757871e Compare October 24, 2024 08:32
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

Successfully merging this pull request may close these issues.

5 participants