-
Notifications
You must be signed in to change notification settings - Fork 914
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
Tracing updates for Ruby 2.6 #6149
Labels
Comments
headius
added a commit
that referenced
this issue
Mar 29, 2020
headius
added a commit
that referenced
this issue
Mar 29, 2020
headius
added a commit
that referenced
this issue
Mar 29, 2020
RubySpec TracePoint specs
MRI suite``` 1) Failure: TestTracer#test_tracer_with_option_r [/home/travis/build/jruby/jruby/test/mri/test_tracer.rb:9]: Expected /rubygems\/core_ext\/kernel_require\.rb:\d+:Kernel:<:/ to match nil. 2) Failure: TestTracer#test_tracer_with_option_r_without_gems [/home/travis/build/jruby/jruby/test/mri/test_tracer.rb:21]: unexpected output from `ruby --disable-gems -rtracer -e 1`. <1> expected but was <0>. 3) Failure: TestSetTraceFunc#test_lineno_in_optimized_insn [/home/travis/build/jruby/jruby/test/mri/ruby/test_settracefunc.rb:1919]: [Bug #14809]. <"7\n"> expected but was <"">. 4) Failure: TestSetTraceFunc#test_tracepoint_nested_enabled_with_target [/home/travis/build/jruby/jruby/test/mri/ruby/test_settracefunc.rb:1998]: <"can't nest-enable a targetting TracePoint"> expected but was <"wrong number of arguments calling `enable` (given 1, expected 0)">. 5) Error: TestSetTraceFunc#test_script_compiled: ArgumentError: unknown event: script_compiled org/jruby/ext/tracepoint/TracePoint.java:63:in `initialize' org/jruby/RubyClass.java:918:in `new' /home/travis/build/jruby/jruby/test/mri/ruby/test_settracefunc.rb:2094:in `test_script_compiled' 6) Error: TestSetTraceFunc#test_tracepoint_enable_target: ArgumentError: wrong number of arguments calling `enable` (given 1, expected 0) /home/travis/build/jruby/jruby/test/mri/ruby/test_settracefunc.rb:1962:in `check_with_events' /home/travis/build/jruby/jruby/test/mri/ruby/test_settracefunc.rb:1974:in `test_tracepoint_enable_target' 7) Error: TestSetTraceFunc#test_tracepoint_enable_with_target_line: ArgumentError: wrong number of arguments calling `enable` (given 1, expected 0) /home/travis/build/jruby/jruby/test/mri/ruby/test_settracefunc.rb:2075:in `test_tracepoint_enable_with_target_line' 8) Error: TestSetTraceFunc#test_tracepoint_parameters: NoMethodError: undefined method `parameters' for # /home/travis/build/jruby/jruby/test/mri/ruby/test_settracefunc.rb:722:in `block in test_tracepoint_parameters' /home/travis/build/jruby/jruby/test/mri/ruby/test_settracefunc.rb:735:in `block in test_tracepoint_parameters' org/jruby/ext/tracepoint/TracePoint.java:161:in `enable' /home/travis/build/jruby/jruby/test/mri/ruby/test_settracefunc.rb:735:in `test_tracepoint_parameters' ``` |
Note the tracer library needs an update, which may fix those two failures. See ruby/tracer#1 |
Link to #5147, coverage options added in 2.5. |
Like #5147, nobody is jumping on this or other tracing-related issues so we are untargeting. Help wanted! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are a number of tracing updates in Ruby 2.6. We consider them a low-priority item, but I want to track the spec/test excludes.
The text was updated successfully, but these errors were encountered: