aboutsummaryrefslogtreecommitdiffstats
path: root/spec
Commit message (Collapse)AuthorAgeFilesLines
* Warn in verbose mode on defining a finalizer that captures the objectChris Seaton2019-07-031-0/+26
| | | | | | [Feature #15974] Closes: https://github.com/ruby/ruby/pull/2264
* Prefer master rather than trunk in README [ci skip]Takashi Kokubun2019-07-011-1/+1
|
* Fix predicate to assert if object is sameNobuyoshi Nakada2019-06-291-2/+2
|
* Fix predicate to assert if object is sameNobuyoshi Nakada2019-06-291-1/+1
|
* Update to ruby/spec@94d98ffBenoit Daloze2019-06-2710-18/+18
|
* Update to ruby/spec@8d74d49Benoit Daloze2019-06-27157-540/+578
|
* Update to ruby/mspec@ca2bc42Benoit Daloze2019-06-272-3/+3
|
* Expand and clarify documentation about version guards for specsBenoit Daloze2019-06-271-5/+35
|
* Added version guard for backtrace printing feature of psych to ruby/spec.Hiroshi SHIBATA2019-06-261-2/+10
|
* Fixed broken ruby/spec related a53ab897c35586a836710a8afeb1e8c1abd9b087Hiroshi SHIBATA2019-06-251-1/+1
|
* Max length of UNIX socket path is 104 bytes on macOSNobuyoshi Nakada2019-06-231-2/+2
|
* Do not lengthen UNIX socket pathNobuyoshi Nakada2019-06-231-1/+1
| | | | | * spec/ruby/library/socket/unixsocket/recvfrom_spec.rb: do not lengthen UNIX socket path, which is very stricted.
* Alias ENV.merge! as ENV.updateKenichi Kamiya2019-06-213-21/+31
| | | | | | [Feature #15947] Closes: https://github.com/ruby/ruby/pull/2246
* Use different names for autoload constants in specs for clarityBenoit Daloze2019-06-211-4/+4
|
* Add extra spec from https://github.com/ruby/ruby/pull/2173Jean Boussier2019-06-211-0/+5
|
* Add an optional `inherit` argument to Module#autoload?Jean Boussier2019-06-212-0/+18
| | | | | | [Feature #15777] Closes: https://github.com/ruby/ruby/pull/2173
* Remove spec testing undefined behaviorJeremy Evans2019-06-191-5/+0
| | | | Fixes [Bug #15432]
* Implement Complex#<=>Jeremy Evans2019-06-191-0/+27
| | | | | | | | | | | Implement Complex#<=> so that it is usable as an argument when calling <=> on objects of other classes (since #coerce will coerce such numbers to Complex). If the complex number has a zero imaginary part, and the other argument is a real number (or complex number with zero imaginary part), return -1, 0, or 1. Otherwise, return nil, indicating the objects are not comparable. Fixes [Bug #15857]
* Fixed the code-style with the upstream rule.Hiroshi SHIBATA2019-06-111-4/+4
|
* Resolv specs should pass on Windows nowBenoit Daloze2019-06-104-26/+18
|
* Fix Resolv specs to not depend on a system /etc/hosts fileBenoit Daloze2019-06-105-15/+16
| | | | | * https://rubyci.org/logs/rubyci.s3.amazonaws.com/archlinux/ruby-master/log/20190609T153804Z.fail.html.gz * Thanks @naruse for the tip.
* Fixed wrong BUNDLE_BIN_PATH for ruby core.Hiroshi SHIBATA2019-06-091-1/+1
|
* Added the condition for ruby_core repository.Hiroshi SHIBATA2019-06-092-2/+15
|
* Merge bundler master from upstream.Hiroshi SHIBATA2019-06-0962-678/+730
| | | | Pick from 8dd59e3ba97eb80a599f8149f31bf40773b69dc0
* Make specs pass on OpenBSDJeremy Evans2019-06-064-67/+118
| | | | | | | | | | | | | | | | | Skip Process clockres specs that don't work on either FreeBSD or Solaris/AIX in addition to OpenBSD. Run most current String#crypt specs on non-OpenBSD, and add a new set of crypt specs for OpenBSD, which support bcrypt but not DES in crypt(3). Use @server.connect_address instead of @server.getsockname in some socket tests, as OpenBSD does not treat connection to all zero IPv4 or IPv6 addresses as connection to localhost. When trying to connect using UDP on an unsupported address family, allow Errno::EPROTONOSUPPORT in addition to Errno::EAFNOSUPPORT, as OpenBSD raises the former.
* spec/bundler/bundler/dsl_spec.rb: fix exception to raiseNobuyoshi Nakada2019-06-051-2/+2
| | | | When describing "Runtime errors", raise a `RuntimeError` as-is.
* Split an assertion for f1f04caf60e4fc9dc3b12109e0be831f2d692810Nobuyoshi Nakada2019-06-051-1/+2
|
* `ruby -v` may no longer be ASCII-only on non-master branchesNobuyoshi Nakada2019-06-031-1/+1
|
* Update to ruby/spec@cfe908cBenoit Daloze2019-05-311-0/+35
|
* Update to ruby/mspec@a57a9afBenoit Daloze2019-05-311-42/+13
|
* Let irb use an empty file as irbrcNobuyoshi Nakada2019-05-312-1/+3
| | | | to get rid of side-effect by existing .irbrc file.
* UNIX domain socket name length has a certain limitNobuyoshi Nakada2019-05-311-1/+6
|
* Update to ruby/spec@0ba5312Benoit Daloze2019-05-303-29/+58
|
* Update to ruby/mspec@3cc36d0Benoit Daloze2019-05-303-11/+7
|
* Skip spec broken since a66bc2c01194a9c017c874a30db5b3b6bd95e966Takashi Kokubun2019-05-291-23/+27
| | | | This has not worked since the merge https://travis-ci.org/ruby/ruby/jobs/538438184
* Fix shorten-64-to-32 warningNobuyoshi Nakada2019-05-291-1/+1
|
* Update to ruby/spec@0c5c5c1Benoit Daloze2019-05-281-7/+3
|
* Update to ruby/spec@9a501a8Benoit Daloze2019-05-2841-639/+699
|
* Add FrozenError#receiverJeremy Evans2019-05-261-0/+34
| | | | | | | | | | | | | | | | | Similar to NameError#receiver, this returns the object on which the modification was attempted. This is useful as it can pinpoint exactly what is frozen. In many cases when a FrozenError is raised, you cannot determine from the context which object is frozen that you attempted to modify. Users of the current rb_error_frozen C function will have to switch to using rb_error_frozen_object or the new rb_frozen_error_raise in order to set the receiver of the FrozenError. To allow the receiver to be set from Ruby, support an optional second argument to FrozenError#initialize. Implements [Feature #15751]
* Add notes for the Process#clock_getres specBenoit Daloze2019-05-241-1/+4
|
* Only exclude the failing clocks for Process.clock_getres specs on AIXBenoit Daloze2019-05-242-1/+8
| | | | * https://rubyci.org/logs/rubyci.s3.amazonaws.com/aix71_ppc/ruby-trunk/log/20190522T103301Z.fail.html.gz
* Skip the Process.clock_getres spec on AIXYusuke Endoh2019-05-241-1/+1
| | | | https://rubyci.org/logs/rubyci.s3.amazonaws.com/aix71_ppc/ruby-trunk/log/20190522T103301Z.fail.html.gz
* Add `Time#ceil`.manga_osyo2019-05-231-0/+45
| | | | Closes: https://github.com/ruby/ruby/pull/2133
* Adding Enumerable#filter_mapAlfonso Jiménez2019-05-231-0/+26
| | | | | [Feature #15323] Closes: https://github.com/ruby/ruby/pull/2017
* spec/ruby/core/hash/constructor_spec.rb: add "ruby_version_is" guardYusuke Endoh2019-05-231-7/+20
| | | | follow up for d3f1c615c5
* hash.c (rb_hash_s_create): Reject `Hash[[nil]]`Yusuke Endoh2019-05-231-2/+2
| | | | | | | The behavior of `Hash[[nil]] #=> {}` was a bug until 1.9.3, but had been remained with a warning because some programs depended upon it. Now, six years passed. We can remove the compatibility behavior. [Bug #7300]
* Eagerly name modules and classesAlan Wu2019-05-221-0/+36
| | | | | | | | | | | | | | | | | | | | | | | * variable.c: make the hidden ivars `classpath` and `tmp_classpath` the source of truth for module and constant names. Assign to them when modules are bind to constants. * variable.c: remove references to module name cache, as what used to be the cache is now the source of truth. Remove rb_class_path_no_cache(). * variable.c: remove the hidden ivar `classid`. This existed for the purposes of module name search, which is now replaced. Also, remove the associated rb_name_class(). * class.c: use rb_set_class_path_string to set the name of Object during boot. Must use a fstring as this runs before rb_cString is initialized and creating a normal string leads to a VALUE without a class. * spec/ruby/core/module/name_spec.rb: add a few specs to specify what happens to Module#name across multiple operations. These specs pass without other code changes in this commit. [Feature #15765]
* Remove redundant ignore rule for Process#clock_getres specsBenoit Daloze2019-05-201-7/+0
|
* Move exclusion for Hyper-V next to other skipped constantsBenoit Daloze2019-05-202-6/+9
|
* skip a test for CLOCK_MONOTONIC_RAW.Koichi Sasada2019-05-201-1/+6
| | | | | | | | | | | | | On my Linux guest machine on Hyper-V, I got an error. Process.clock_gettime(CLOCK_MONOTONIC_RAW, :nanosecond) returns like: ... 875573945119100 875573945119600 ... even if `Process.clock_getres(value, :nanosecond)` returns 1. So I simply skip this test for CLOCK_MONOTONIC_RAW.