[WIP] Add a test case for module name in rb_profile_frame_classpath #9

This is a follow-up of 83240f3 .

The user management on Android seems very different https://rubyci.org/logs/rubyci.s3.amazonaws.com/android28-x86_64/ruby-master/log/20200416T234122Z.fail.html.gz

Just cast down explicitly.

* renamed argument `writable` as `waiting` * hosited out creating and raising exception * turned into a `switch`

Instead of letting callers rescue the error always.

Deprerecated constants which had been warned since 2.4.

This is follow up of 62554ca

We failed to ignore https://ci.appveyor.com/project/ruby/ruby/builds/32245902/job/xcfxw67uexxysvni

According to warnings on Travis, there's no such key. We handle this on webhook side anyway.

In the last 26-ish hours, it has failed 5 times: https://travis-ci.org/github/ruby/ruby/jobs/676497718 https://travis-ci.org/github/ruby/ruby/jobs/676480295 https://travis-ci.org/github/ruby/ruby/jobs/676103216 https://travis-ci.org/github/ruby/ruby/jobs/676057967 https://travis-ci.org/github/ruby/ruby/jobs/676055113 and I don't think anybody has been working on it right now. To make CI result report of s390x-linux useful, let's skip it until the test is improved to be more stable.

Slightly simplifying 8d6aa06

…uby.py

on stack when local_stack_p is enabled. This fixes `RB_FL_TEST_RAW:"RB_FL_ABLE(obj)"` assertion failure on power_assert's test with JIT enabled.

ruby/reline@d563063ea0

ruby/reline@cab312f584

ruby/reline@8480db575b

ruby/reline@e9ae288825

ruby/reline@ca750b676b

Only the names are case-sensitive.

MSP-Greg/actions-ruby is deprecated...

https://ci.appveyor.com/project/ruby/ruby/builds/32278754/job/90jmky2jq2k0wjv8

The test fails due to unknown reason. Need to debug in future, but tentatively skipped.

... just like AIX and OpenBSD.

Since this commit (ruby@9e1b06e), the VM Debug Level constant is moved from `vm_insnhelper.h` to `vm_core.h`. This PR is a super tiny update to reflect that change so that people won't waste time on searching in a wrong file.

VMDEBUG is always defined as defaulted to 0 in vm_core.h.

As atomic operations are mandatory now, not-working phony fallback definitions are not only useless but confusing and harmful.

[ci skip]

Currently, objdump -W miniruby emits some errors on riscv, so I guess that DWARF is corrupted.

https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian-riscv64/ruby-master/log/20200420T083601Z.fail.html.gz

[Bug #15359][ruby-core:90164]

NoMemoryError is observed on icc but I fail to reproduce so far. Let me see the backtrace on CI.

Ditto for 4b85393

NDEBUG can be defined via a command-line argument. Should take care of such situations.

Ditto for adab82b. TRY_WITH_GC was found innocent.

Now, the order is good, old-fashioned style: ``` $ ./local/bin/ruby -e 'def foo; raise; end def bar; foo; end def baz; bar; end def qux; baz; end qux ' -e:1:in `foo': unhandled exception from -e:2:in `bar' from -e:3:in `baz' from -e:4:in `qux' from -e:5:in `<main>' ```

Since it is impossible to detect stack overflow of C functions robustly, the test is a bit unreasonable. https://rubyci.org/logs/rubyci.s3.amazonaws.com/debian-riscv64/ruby-master/log/20200421T120018Z.fail.html.gz

as well as e62aead

# Iteration per second (i/s) | |compare-ruby|built-ruby| |:------------|-----------:|---------:| |float | 30.395M| 38.314M| | | -| 1.26x| |float_true | 3.833M| 27.322M| | | -| 7.13x| |float_false | 4.182M| 24.938M| | | -| 5.96x|

This reverts commit 6b04c48. Trailing spaces separate paragraphs in RDoc format.

This reverts commit 67bcac8.

Even for empty argument list, not to be confusing with a writer method name.

https://github.com/ruby/actions/runs/608526685?check_suite_focus=true `warning: Insecure world writable dir /home/runner/.config in PATH, mode 040777`

search_method() can return invalid method, but vm_defined() checks it as valid method entry. This is why defined?(foo) if foo is undef'ed. To solve this problem, check invalidation and return NULL. [Bug #16669] https://twitter.com/kamipo/status/1252881930103558144 Tests will be merged by nobu soon.

As well as worker processes do in Test::Unit::Worker#run.

* `RbConfig::CONFIG['ridir']` has been set since 1.9.2 * `ENV["HOME"]` has been defaulted to `USERPROFILE` since 1.9.0, and backported to 1.8.5 or later. ruby/rdoc@a3a614e676

* Support XDG_CONFIG_HOME for gemrc. * Support XDG_DATA_HOME for .gem * Added test for XDG_DATA_HOME * Do not reuse environmental variable. * Unify .rdoc path to RDoc.home. * Support XDG_DATA_HOME for .rdoc * Ignore exists? * Extracted config_home path * Use XDG_CONFIG_HOME for default credential path * Fixed inconsistency location. * Fixed the broken tests. * Support XDG_CONFIG_HOME for irbrc * Introduce Gem.cache_home as XDG_CACHE_HOME * Use Gem.cache_home instead of Gem.config_home for the credential file of RubyGems. * Initialized the old configurations * Fixed test failure related the configuration initialization * restore XDG_DATA_HOME * Fixed the broken examples of bundler with XDG_* * Do not modify environmental variable on test file * Use XDG_DATA_HOME insted of XDG_CACHE_HOME for credential file * stub out Gem.data_home * Move dir accessor to defaults.rb file * Use XDG_DATA_HOME for signed gem features * Use XDG_DATA_HOME for spec cache * Do not rely on Gem.user_home * Gem.user_home is always exists. Don't need to use FileUitls.mkdir_p * Bump support version to RubyGems 3.2.0+ * Removed the needless fallback configuration * Fixed the inconsistency methods that are find_config_file and config_file * Use Gem.configuration.credentials_path instead of hard-coded path * gem_path is always provided * Removed the duplicated code of find_home * Also removed the duplicated code of user_home * use Gem::UNTAINT instead of untaint for surpressing the warnings * Use File.directory * Restore XDG_DATA_HOME * Use File.write

In the XDG Specification, if ~/.config/readline/inputrc exists, then ~/.inputrc should not be read, but for compatibility with GNU Readline, if ~/.inputrc exists, then it is given priority. ruby/reline@97f1e7db04

ruby/reline@9b1327d2f4

ruby/rdoc@00fb4dd2a3

ruby/rdoc@6c4801d1f6

[ci skip]

https://rubyci.org/logs/rubyci.s3.amazonaws.com/scw-ad7f67/ruby-master/log/20200425T175405Z.fail.html.gz ``` 4) Error: TestRDocServlet#test_asset: NoMethodError: undefined method `replace' for nil:NilClass /home/chkbuild/build/20200425T175405Z/ruby/test/rdoc/test_rdoc_servlet.rb:48:in `setup' 5) Error: TestRDocServlet#test_asset: NoMethodError: undefined method `replace' for nil:NilClass /home/chkbuild/build/20200425T175405Z/ruby/test/rdoc/test_rdoc_servlet.rb:63:in `teardown' ``` ... ``` 74) Error: TestRDocServlet#test_store_for_site: NoMethodError: undefined method `replace' for nil:NilClass /home/chkbuild/build/20200425T175405Z/ruby/test/rdoc/test_rdoc_servlet.rb:48:in `setup' 75) Error: TestRDocServlet#test_store_for_site: NoMethodError: undefined method `replace' for nil:NilClass /home/chkbuild/build/20200425T175405Z/ruby/test/rdoc/test_rdoc_servlet.rb:63:in `teardown' ```

yield `home_dir` when HOMEDIR is not falsy only. https://github.com/ruby/ruby/blob/d0f41aa2382612022162d033ddb3d9c9cc62099e/lib/rdoc/ri/paths.rb#L43 ``` yield home_dir, :home if home and HOMEDIR ``` https://rubyci.org/logs/rubyci.s3.amazonaws.com/archlinux/ruby-master/log/20200426T033503Z.fail.html.gz ``` 1) Failure: TestRDocRIPaths#test_class_each [/home/chkbuild/build/20200426T033503Z/ruby/test/rdoc/test_rdoc_ri_paths.rb:54]: <nil> expected but was <"/home/naruse/chkbuild/tmp/build/20200426T033503Z/tmp/test_rdoc_ri_paths_1033468/doc/nodoc-1.0/ri">. 2) Failure: TestRDocRIPaths#test_class_raw_path [/home/chkbuild/build/20200426T033503Z/ruby/test/rdoc/test_rdoc_ri_paths.rb:131]: <nil> expected but was <"/home/naruse/chkbuild/tmp/build/20200426T033503Z/tmp/test_rdoc_ri_paths_1033468/doc/rake-10.0.1/ri">. 3) Failure: TestRDocRIPaths#test_class_raw_path_extra_dirs [/home/chkbuild/build/20200426T033503Z/ruby/test/rdoc/test_rdoc_ri_paths.rb:141]: <nil> expected but was <"/home/naruse/chkbuild/tmp/build/20200426T033503Z/tmp/test_rdoc_ri_paths_1033468/doc/rake-10.0.1/ri">. ```

Revert 9948add. It is now discussed in https://bugs.ruby-lang.org/issues/16814, and an assert is added with a217d3c. It would be good to give it a try.

That bug has been fixed by ec0c394, and the test has been added by 181ffea.

Couldn't figure out failed/fixed versions.

English.rb is extracted to the default gems at ruby@2c5764e rubygems/rubygems@532f488c0b

Some tests had failed under `umask 077` mode. As far as I investigated, there is no actual bug. All failures were caused by tests that create a wrong-permission file or expect wrong permission. This changeset fixes the tests. rubygems/rubygems@078213e527

rubygems/rubygems@42aa0d7ebc

rubygems/rubygems@d4486ca061

Even without this limit, these assertions almost certainly cause a NoMemoryError by removing the fix in 72ad859.

Partially revert adab82b and c63b5c6. The issue that these commits attempt to address was maybe fixed with 1c7f5a5.

It may contain symbolic links.

https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html > All paths set in these environment variables must be absolute. > If an implementation encounters a relative path in any of these > variables it should consider the path invalid and ignore it. ruby/reline@45af6eea77

ruby/reline@9bdbed9cbc

And unlimited is default. ruby/reline@f5149c3ca6

ruby/reline@298144b06a

ruby/reline@13420197b8

ruby/irb@a6fe58e916

ruby/irb@cdbb9dfc9f

ruby/irb@5f0aee56fa

Readline::VERSION may not be a single word, e.g EditLine wrapper when linked with editline.

IRB::ReadlineInputMethod#initialize sets via IRB.set_encoding.

Running C compiler for JIT compaction inside a critical section may lock main thread for a long time when it triggers GC. As I'm planning to increase this duration a bit, I'd like to make sure this doesn't stop the world. For now, I chose to give up unloading units when it's during JIT compaction, assuming other calls may unload them later.

because we support JIT compaction on it

I'm trying to make it possible to include all JIT-ed code in a single C file. This is needed to guarantee uniqueness of all function names

Patch adapted from Alessandro Minali

to child compile_status

to improve code locality. Using benchmark-driver/sinatra with 100 methods JIT-ed, [Before] 12149.97 rps 1.3M /tmp/_ruby_mjit_p31171u145.so [After] 12818.83 rps 260K /tmp/_ruby_mjit_p32155u145.so (VM is 13714.89 rps)

as well. And also unit->c_file doesn't exist in mswin. https://github.com/ruby/ruby/runs/635915704

As zero variadic macro argument, `rb_scan_args(argc, argv, "")` (or `"0"`), means 0-arity method and should be defined so, that case doesn't need to consider.

to fix https://ci.appveyor.com/project/ruby/ruby/builds/32577700/job/yh61rom35wt2uv39 It was for JIT compaction, and we don't support it on mswin.

caused by 818d6d3, for now. I'll take a look at them tomorrow.

Also renamed as like as a constant.

to be investigated later https://rubyci.org/logs/rubyci.s3.amazonaws.com/solaris10-gcc/ruby-master/log/20200501T160004Z.fail.html.gz

As fork(2) is deprecated, its calls must be guarded by `COMPILER_WARNING_IGNORED(-Wdeprecated-declarations)`. All usages of fork(2) in process have been alread guarded. A new call to fork(2) was added in ruby.c with f22c4ff. This caused a build failure on Solaris 11. It may hide a bug to guard big code unnecessarily, so this change introduces a simple wrapper "rb_fork" whose definition is guarded, and replaces all calls to fork(2) with the wrapper function.

* Fixes [Bug #16826]

The exact exit status value of command failed to run is not a spec, but a platform dependent implementation detail. Just it is not "success".

Android is Linux, but the clock resolution is 10 milliseconds. I think that 1 microsecond is too strict for embedded environment. This change laxes the limit to 10 milliseconds.

It's to avoid memory leak for actual usage (because they don't get unloaded properly), but also for fixing CI timed out due to JIT compaction taking too long time on --jit-wait (which runs every time) http://ci.rvm.jp/results/trunk-mjit-wait@silicon-docker/2911601

`RUBY_FL_SEEN_OBJ_ID` can be set by #object_id.

GCC/Clang can optimize to calculate `sin(x)` and `cos(x)` at once, when the both are closely called on the same argument. Similar optimization is possible for `__sinpi(x)` and `__cospi(x)` if available, which calculate arguments in radian, i.e. `sin(x*M_PI)` and `cos(x*M_PI)` respectively.

Fix https://github.com/ruby/ruby/runs/636020145 without skipping too many tests. It seems that .c -> .o with debug flags and .o -> .so without debug flags did not generate .dSYM but now .c -> .so with debug flags seems to generate a .dSYM directory. As --jit-debug should not be used by normal users, let me skip implementing the removal for now.

It turned out that the pdb corruption happens on Visual Studio 2015 as well. https://ci.appveyor.com/project/ruby/ruby/builds/32602953/job/3gj43q18wqeiy729

This support was accidentally removed in 818d6d3.

And utilize more bits even if DBL_MANT_DIG > 53.

An expression using `static const` value seems not considered as `static const` by Visual C.

It has caused errors by ENOSPC like https://travis-ci.org/github/ruby/ruby/jobs/682520961 too often. I cleared all cache of Travis yesterday, but it didn't help it. Until somebody figures out how to fix it, let me exclude it from CI status reports to avoid false alerts.

using -Winvalid-pch https://rubyci.org/logs/rubyci.s3.amazonaws.com/solaris10-gcc/ruby-master/log/20200501T170004Z.fail.html.gz

MinGW test_jit fails with no error message. Perhaps linker flags should not be passed when compilation is happening. Anyway splitting these stages doesn't matter for performance. So let me just split it to fix the issue. Probably this helps Solaris's issue too.

I think 9aa5fe1 helps this issue too.

For some reason 0776198 didn't fail https://rubyci.org/logs/rubyci.s3.amazonaws.com/solaris10-gcc/ruby-master/log/20200503T230004Z.log.html.gz even while it was before 9aa5fe1. Anyway, there's no need to keep the change anymore.

* Folding results should not be empty. If `OnigCodePointCount(to->n)` were 0, `for` loop using `fn` wouldn't execute and `ncs` elements are not initialized. ``` enc/unicode.c:557:21: warning: 'ncs[0]' may be used uninitialized in this function [-Wmaybe-uninitialized] 557 | for (i = 0; i < ncs[0]; i++) { | ~~~^~~ ``` * Cast to `enum yytokentype` Additional enums for scanner events by ripper are not included in `yytokentype`. ``` ripper.y:7274:28: warning: implicit conversion from 'enum <anonymous>' to 'enum yytokentype' [-Wenum-conversion] ```

Due to the change in 3893a8d, there is no longer a need to put true/false.

We only need to loop `T_MASK` times once. Also, not every value between 0 and `T_MASK` is an actual Ruby type. Before this change, some integers were being added to the result hash even though they aren't actual types. This patch omits considered / moved entries that total 0, cleaning up the result hash and eliminating these "fake types".

https://bugs.ruby-lang.org/issues/16830 ruby/uri@b4bf8c1217

…_values. [DOC] [#16829]

* rb_equal() already checks using `obj1 == obj2`.

* Multiple times people have been confused and believed rb_equal() called #=== but it does not, it calls #==. * This optimization has a subtle side effect for Float::NAN, which is now documented.

…ization

`rb_equal` may be inlined in `case_equal` and actually same code is generated twice.

As now `Object#===` document is separated from `rb_equal`, this note no longer makes sense.

It is more popular than /proc/self/fd.

`getaddrinfo` on macOS seems keeping FDs to query host names internally.

To get rid of calling `getaddrinfo`, which may keep FDs internally.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[WIP] Add a test case for module name in rb_profile_frame_classpath #9

[WIP] Add a test case for module name in rb_profile_frame_classpath #9

Commits on Apr 16, 2020

Commits on Apr 17, 2020

Commits on Apr 18, 2020

Commits on Apr 19, 2020

Commits on Apr 20, 2020

Commits on Apr 21, 2020

Commits on Apr 22, 2020

Commits on Apr 23, 2020

Commits on Apr 24, 2020

Commits on Apr 25, 2020

Commits on Apr 26, 2020

Commits on Apr 27, 2020

Commits on Apr 28, 2020

Commits on Apr 29, 2020

Commits on Apr 30, 2020

Commits on May 1, 2020

Commits on May 2, 2020

Commits on May 3, 2020

Commits on May 4, 2020

Commits on May 5, 2020

Commits on May 6, 2020