summaryrefslogtreecommitdiff
path: root/spec/ruby/core
AgeCommit message (Collapse)Author
2020-02-22Expand Symbol#to_proc specs to be clearerBenoit Daloze
2020-02-22Proc from Symbol needs a receiverNobuyoshi Nakada
So its arity should be -2 instead of -1. [Bug #16640] https://bugs.ruby-lang.org/issues/16640#change-84337
2020-02-19`Proc` made by `Symbol#to_proc` should be a lambda [Bug #16260]Nobuyoshi Nakada
2020-02-13spec/ruby: skip the specs that use /etc/passwd on AndroidYusuke Endoh
There is no /etc/passwd on Android
2020-02-13spec/ruby/core/process/spawn_spec.rb: Use / instead of /tmpYusuke Endoh
because there is no /tmp on Android.
2020-02-13spec/ruby/core/process/clock_getres_spec.rb: skip on AndroidYusuke Endoh
in the same way as FreeBSD and OpenBSD. I guess that the spec makes too strong assumption.
2020-02-13spec/ruby/core/encoding/locale_charmap_spec.rb: locale_charmap is UTF-8 on ↵Yusuke Endoh
Android nl_langinfo(CODESET) always returns UTF-8 on Android, regardless to LC_ALL=C.
2020-02-13spec/ruby/core/dir/home_spec.rb: exclude AndroidYusuke Endoh
I couldn't find a robust way to get the home path except ENV["HOME"] on Android Termux.
2020-02-09spec/ruby/core/file/utime_spec.rb: far future timestamp may be trancatedYusuke Endoh
Under some Ext4 filesystem settings, a timestamp is limited up to 0x37fffffff (2446-05-10). https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Inode_Timestamps > Therefore, timestamps should not overflow until May 2446. Actually the spec fails under one of our CI environments, like: ``` 1) File.utime allows Time instances in the far future to set mtime and atime FAILED Expected 2446 == 559444 to be truthy but was false ``` https://rubyci.org/logs/rubyci.s3.amazonaws.com/arch/ruby-master/log/20200208T180002Z.fail.html.gz
2020-02-06[ruby/spec] Just test that sleep completesNobuyoshi Nakada
2020-02-06[ruby/spec] Check by Thread#stop?Nobuyoshi Nakada
Check if threads are stopped by Thread#stop? instead of the status name.
2020-01-28Update to ruby/spec@f8a2d54Benoit Daloze
2020-01-28Fix version guard in __dir__ specBenoit Daloze
2020-01-27Removed useless "spec"sNobuyoshi Nakada
It is not specific to particular methods that keyword option arguments are coerced to `Hash`es using `to_hash` method.
2020-01-26Moved Array#sample to rbincNobuyoshi Nakada
2020-01-26Moved Array#shuffle and Array#shuffle! to rbincNobuyoshi Nakada
2020-01-25spec/ruby/core/process/times_spec.rb: add an output code for debuggingYusuke Endoh
2020-01-15Update version guardKazuhiro NISHIYAMA
fix up 98ef38ada43338c073f50a0093196f0356284625
2020-01-15Freeze Regexp literalsJean Boussier
[Feature #8948] [Feature #16377] Since Regexp literals always reference the same instance, allowing to mutate them can lead to state leak. Notes: Merged: https://github.com/ruby/ruby/pull/2705
2020-01-09Include the standard `id` command outputNobuyoshi Nakada
On macOS, GNU coreutils `id` is limited to NGROUPS_MAX groups, because of the backward compatibility of getgroups(2).
2020-01-03Make eval(code, binding) use (eval) as __FILE__ and 1 as __LINE__Jeremy Evans
This removes the warning that was added in 3802fb92ff8c83eed3e867db20f72c53932f542d, and switches the behavior so that the eval does not use the binding's __FILE__ and __LINE__ implicitly. Fixes [Bug #4352] Notes: Merged: https://github.com/ruby/ruby/pull/2816
2020-01-02Update specs for keyword argument separationJeremy Evans
Notes: Merged: https://github.com/ruby/ruby/pull/2794
2019-12-30Fix Proc#<< specAlan Wu
[Bug #16406]
2019-12-30Decide lambdaness of (f << g) using g (#2729)Alan Wu
* Deciding lambdaness of (f << g) using g * Use version guards for spec changes Notes: Merged-By: XrXr
2019-12-27Update to ruby/spec@7241f39Benoit Daloze
2019-12-27Update to ruby/spec@d419e74Benoit Daloze
2019-12-24Get rid of false positive misspellingsNobuyoshi Nakada
[Bug #16437]
2019-12-23Revert "Should return "." for File.extname("file.") also on Windows"NAKAMURA Usaku
We want to introduce consistency and better compatibility with unixen, but the Windows APIs doues not have consistency fundamentally and we can not found any logical way... This reverts commit 61aff0cd189e67fa6f2565639ad0128fa33b88fc.
2019-12-22Move version guard outside to make it clear the method was added in Ruby 2.5Benoit Daloze
2019-12-22Should return "." for File.extname("file.") also on WindowsNAKAMURA Usaku
But not changes another cases, such as "file.rb." [Bug #15267]
2019-12-21Add spec for capturing Kernel#lambda with Kernel#methodAlan Wu
Notes: Merged: https://github.com/ruby/ruby/pull/2289
2019-12-21Add specs for calling into Kernel#lambda with superAlan Wu
Notes: Merged: https://github.com/ruby/ruby/pull/2289
2019-12-20Makes the receiver to FrozenError.new a keyword parameterNobuyoshi Nakada
[Feature #16419]
2019-12-20Fixed misspellingsNobuyoshi Nakada
Fixed misspellings reported at [Bug #16437], only in ruby and rubyspec.
2019-12-11Test `Thread#to_s` when used from to_s_spec.rbNobuyoshi Nakada
2019-12-11`Thread#to_s` has been added at ruby 2.5Nobuyoshi Nakada
2019-12-11Thread#to_s is not same as #inspect on old version.Koichi Sasada
Thread#to_s returns simple Object#to_s until Ruby 2.4.
2019-12-11fix for old MRI versionsKoichi Sasada
2019-12-11Make Thread#to_s consistent with Method and Proc to_sJean byroot Boussier
Notes: Merged: https://github.com/ruby/ruby/pull/2738
2019-12-04Revert "Regexp#match{?} with nil raises TypeError as String, Symbol (#1506)"NARUSE, Yui
This reverts commit 2a22a6b2d8465934e75520a7fdcf522d50890caf. Revert [Feature #13083]
2019-12-04Revert "Revert nil error and adding deprecation message"NARUSE, Yui
This reverts commit 452bee3ee8d68059fabd9b1c7a75661b14e3933e.
2019-12-04Revert "Improve warning message"NARUSE, Yui
This reverts commit 31110d820cc1258cbc84b46ecc65b254c7d5529a.
2019-12-04Revert "Fix warnings in Regexp#{match,match?} specs"NARUSE, Yui
This reverts commit 782d1b8fb0a039cedef9ad9c94f432dad51901e6.
2019-12-02Make more attempts to check for the precision of Process.timesBenoit Daloze
* Process.clock_getres specs use 10_000 but that's quite slow for the Process.times spec.
2019-12-02Fix random failure on getusage-missing environmentsTakashi Kokubun
`* 1e6` makes a spurious result about floating point number's precision. ``` irb(main)[01:0]> 16.028 => 16.028 irb(main)[02:0]> (16.028 * 1e6) => 16027999.999999998 ```
2019-12-01Debug random failure of ruby-spec on ci.rvm.jpTakashi Kokubun
2019-12-01Update to ruby/spec@dcf4955Benoit Daloze
2019-12-01[ruby/spec] Fix failures with LC_ALL=CNobuyoshi Nakada
https://github.com/ruby/spec/commit/51047687c0 https://github.com/ruby/spec/commit/2b87b467cc
2019-11-30Skip if getrusage is not supportedTakashi Kokubun
1243255c3a36433041012b6107a5ac48658a0895 broke ci.rvm.jp tests like http://ci.rvm.jp/results/trunk_clang_39@silicon-docker/2445098. 253232c028a5565dbeecc05fab5e81b35ab58bcc works only if getrusage is supported.
2019-11-30Update to ruby/spec@4eec3dcBenoit Daloze
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-28 04:03:51 +0000