summaryrefslogtreecommitdiff
path: root/spec
Commit message (Collapse)AuthorAgeFilesLines
* Fix indentationKazuki Tsujimoto2020-11-071-187/+187
|
* Fix and remove spec testing undefined behaviorKazuki Tsujimoto2020-11-071-34/+8
|
* Revert "Make `marshal_load` public"Marc-Andre Lafortune2020-11-041-1/+1
| | | | | | This reverts commit ee7cc6ac35cfb056b3946b1dcd6d4d5a140ccacf. I'm not sure I agree with the spec, but I just tweaked it.
* Make Array methods return Array instances instead of subclass instancesJeremy Evans2020-11-034-28/+86
| | | | | | | | | | | | | | | | This changes the following methods to return Array instances instead of subclass instances: * Array#drop * Array#drop_while * Array#flatten * Array#slice! * Array#slice/#[] * Array#take * Array#take_while * Array#uniq * Array#* Fixes [Bug #6087]
* Use the suppress_warning helper instead of doing it manuallyKazuki Tsujimoto2020-11-011-4/+1
|
* Suppress "One-line pattern matching is experimental" warningKazuki Tsujimoto2020-11-011-4/+9
|
* Fix Rubyspec (ruby-2.7) failuresKazuki Tsujimoto2020-11-013-11/+41
| | | | https://github.com/ruby/ruby/runs/1337845174
* use one-line pattern matching for warning testsKoichi Sasada2020-11-013-7/+5
|
* Assoc pattern matching (#3703)Nobuyoshi Nakada2020-10-264-11/+13
| | | | | [Feature #17260] One-line pattern matching using tASSOC R-assignment is rejected instead.
* Ignore <internal: entries from core library methods for Kernel#warn(message, ↵Benoit Daloze2020-10-262-0/+30
| | | | | | uplevel: n) * Fixes [Bug #17259]
* Add specs that #caller and #caller_locations include core library methods ↵Benoit Daloze2020-10-262-0/+24
| | | | defined in Ruby
* Update to ruby/spec@b164536Benoit Daloze2020-10-261-0/+57
|
* Remove spec which is too difficult to get working with various compilersBenoit Daloze2020-10-262-14/+0
| | | | * The spec means to use an actual system library function, not a wrapper.
* Use gcc-specific pragma only on gcc (and the family)Nobuyoshi Nakada2020-10-261-0/+2
|
* Fix compilation on MSVCNobuyoshi Nakada2020-10-251-9/+4
| | | | | * cast scalar value instead of function * use `rb_pid_t` for the portability
* Try to fix compilation on MSVCBenoit Daloze2020-10-251-0/+6
|
* Update to ruby/spec@4f59d86Benoit Daloze2020-10-2447-61/+725
|
* Update to ruby/mspec@b56e7a2Benoit Daloze2020-10-242-2/+16
|
* numeric.c, range.c: prohibit zero stepKenta Murata2020-10-234-49/+92
| | | | | | | | | * numeric.c: prohibit zero step in Numeric#step * range.c: prohibit zero step in Range#step * Fix ruby-spec [Feature #15573]
* Fix typos [ci skip]Kazuhiro NISHIYAMA2020-10-192-2/+2
|
* Partly reverted test failing with https://github.com/rubygems/rubygems/pull/3921Hiroshi SHIBATA2020-10-151-8/+8
|
* Merge bundler-2.2.0.rc.2Hiroshi SHIBATA2020-10-1545-119/+583
|
* spec/ruby/library/socket/socket/listen_spec.rb: Allow both EACCES and EOPNOSUPPYusuke Endoh2020-10-121-2/+2
| | | | on Android
* relax Fiber#transfer's restrictionKoichi Sasada2020-10-125-38/+113
| | | | | | | | | | | | | | | | | | | | | | | | | Using Fiber#transfer with Fiber#resume for a same Fiber is limited (once Fiber#transfer is called for a fiber, the fiber can not be resumed more). This restriction was introduced to protect the resume/yield chain, but we realized that it is too much to protect the chain. Instead of the current restriction, we introduce some other protections. (1) can not transfer to the resuming fiber. (2) can not transfer to the yielding fiber. (3) can not resume transferred fiber. (4) can not yield from not-resumed fiber. [Bug #17221] Also at the end of a transferred fiber, it had continued on root fiber. However, if the root fiber resumed a fiber (and that fiber can resumed another fiber), this behavior also breaks the resume/yield chain. So at the end of a transferred fiber, switch to the edge of resume chain from root fiber. For example, root fiber resumed f1 and f1 resumed f2, transferred to f3 and f3 terminated, then continue from the fiber f2 (it was continued from root fiber without this patch).
* Make the test suite pass on real Android/Termux environmentYusuke Endoh2020-10-124-5/+17
| | | | Attempting to create a hard link raises EACCES
* Removed meaningless system dependent testsNobuyoshi Nakada2020-10-021-18/+0
| | | | | | As [Bug #16662] lchmod available in linux since glibc 2.31.9000, a system call may exist or not exist depending on the version. It is not a spec nor responsibility of Ruby.
* spec/ruby/core/process/spawn_spec.rb: skip a test on AndroidYusuke Endoh2020-10-011-1/+1
| | | | | | | | | | | | | On Android, STDERR seems to be open even its invoker closes it. http://rubyci.s3.amazonaws.com/android29-x86_64/ruby-master/log/20201001T014315Z.fail.html.gz ``` 1) Process.spawn closes STDERR in the child if :err => :close FAILED Expected (59840): "out\nrescued\n" but got: "out\n" ```
* [ruby/ostruct] Improved YAML serialization.Marc-Andre Lafortune2020-09-301-1/+3
| | | | Patch adapted from Pietro Monteiro [Fixes bug#8382]
* Update to ruby/spec@bfd843aBenoit Daloze2020-09-309-61/+51
|
* Update to ruby/mspec@e154fa1Benoit Daloze2020-09-301-1/+7
|
* Update to ruby/spec@681e8cfBenoit Daloze2020-09-302-8/+10
|
* Update to ruby/mspec@4120a62Benoit Daloze2020-09-301-9/+18
|
* Update to ruby/spec@9277d27Benoit Daloze2020-09-3017-6/+209
|
* Add rb_category_warn{,ing} for warning messages with categoriesJeremy Evans2020-09-282-9/+68
| | | | | | | | | | | | | | | | | | | | | | | | | | | This adds the following C-API functions that can be used to emit warnings with categories included: ```c void rb_category_warn(const char *, const char*, ...) void rb_category_warning(const char*, const char*, ...) ``` Internally in error.c, there is an rb_warn_category function that will call Warning.warn with the string and the category keyword if it doesn't have an arity of 1, and will call Warning.warn with just the string if it has an arity of 1. This refactors the rb_warn_deprecated{,_to_remove} functions to use rb_warn_category. This makes Kernel#warn accept a category keyword and pass it to Warning.warn, so that Ruby methods can more easily emit warnings with categories. rb_warn_category makes sure that the passed category is a already defined category symbol before calling Warning.warn. The only currently defined warning category is :deprecated, since that is what is already used. More categories can be added in later commits.
* Clarify spec description for Hash#{each,each_pair}Benoit Daloze2020-09-281-1/+1
|
* [rubygems/rubygems] Move comment below shebang in bin/console templateSteven Peckins2020-09-281-0/+2
| | | | | | | | | | In an executable script, the shebang line should be the first line (the file needs to start with the bytes 0x23 0x21). Putting a comment above it will break the script. (Regression test included per @deivid-rodriguez) https://github.com/rubygems/rubygems/commit/962e669feb
* freeze all Range objects.v3_0_0_preview1Koichi Sasada2020-09-252-3/+8
| | | | | Matz want to try to freeze all Range objects. [Feature #15504]
* should not check taint flag on rubyspec.Koichi Sasada2020-09-252-2/+6
| | | | | Now taint flag is obsolete and it is used fro shareaable flag. So we should not check this flag.
* Disable deprecation warning by the default [Feature #16345]Nobuyoshi Nakada2020-09-257-32/+48
| | | | And `-w` option turns it on.
* bump Bundler's version to 2.2.0.rc.1Hiroshi SHIBATA2020-09-231-1/+1
|
* Revert "Prevent SystemStackError when calling super in module with activated ↵Jeremy Evans2020-09-221-59/+20
| | | | | | | | | | | | | | refinement" This reverts commit eeef16e190cdabc2ba474622720f8e3df7bac43b. This also reverts the spec change. Preventing the SystemStackError would be nice, but there is valid code that the fix breaks, and it is probably more common than cases that cause the SystemStackError. Fixes [Bug #17182]
* Make Thread#join always convert its argument, as before 70f08f1eedBenoit Daloze2020-09-211-3/+2
|
* Fix Thread leak in Thread#join specsBenoit Daloze2020-09-211-1/+2
|
* Make `Thread#join` non-blocking.Samuel Williams2020-09-211-0/+5
|
* Fix typos [ci skip]Kazuhiro NISHIYAMA2020-09-171-1/+1
| | | | s/overriden/overridden/
* Update to ruby/spec@e829fb0Benoit Daloze2020-09-1727-134/+296
|
* Warn on a finalizer that captures the object to be finalizedChris Seaton2020-09-161-12/+116
| | | | | Also improve specs and documentation for finalizers and more clearly recommend a safe code pattern to use them.
* 2.8 -> 3.0 in specsBenoit Daloze2020-09-15147-201/+199
|
* Interpolated strings are no longer frozen with frozen-string-literal: trueBenoit Daloze2020-09-151-0/+17
| | | | | * Remove freezestring instruction since this was the only usage for it. * [Feature #17104]
* [ruby/ostruct] Fix dup/cloneMarc-Andre Lafortune2020-09-141-0/+2
|
View Lorry Controller Status