aboutsummaryrefslogtreecommitdiffstats
path: root/spec
Commit message (Collapse)AuthorAgeFilesLines
* Skip `File.atime`/`File.mtime` tests randomly failing on TravisNobuyoshi Nakada2022-10-242-9/+11
| | | | | | Not only powerpc64le, also s390x and arm32 seem failing too. These failures are probably caused by filesystem settings on Travis, but unrelated to CPUs.
* [Bug #19004] `Complex.polar` handles complex singular `abs` argumentStephen Ierodiaconou2022-10-231-0/+16
| | | | | | | | | | | | | | | | `Complex.polar` accepts Complex values as arguments for the polar form as long as the value of the complex has no imaginary part (ie it is 'real'). In `f_complex_polar` this is handled by extracting the real part of the arguments. However in the case `polar` is called with only a single argument, the absolute value (abs), then the Complex is created without applying a check on the type of abs, meaning it is possible to create a Complex where the real part is itself an instance of a Complex. This change removes the short circuit for the single argument case meaning the real part extraction is performed correctly (by f_complex_polar). Also adds an example to `spec/ruby/core/complex/polar_spec.rb` to check that the real part of a complex argument is correctly extracted and used in the resulting Complex real and imaginary parts.
* Range#size returns nil for (.."a") and (nil..)Yusuke Endoh2022-10-211-5/+22
| | | | Fixes [Bug #18983]
* Add Class#attached_objectUfuk Kayserilioglu2022-10-201-0/+31
| | | | | | | Implements [Feature #12084] Returns the object for which the receiver is the singleton class, or raises TypeError if the receiver is not a singleton class.
* Followed up CVE-2022-39253 for bundler examplesHiroshi SHIBATA2022-10-203-0/+15
|
* Transition frozen string to frozen root shapeJemma Issroff2022-10-191-1/+1
| | | | Co-Authored-By: Aaron Patterson <tenderlove@ruby-lang.org>
* Merge RubyGems/Bundler masterHiroshi SHIBATA2022-10-188-47/+89
| | | | https://github.com/rubygems/rubygems/commit/6214d00b2315ed37c76b1fbc1c72f61f92ba5a65
* [rubygems/rubygems] Fix bad spec wordingDavid Rodríguez2022-10-181-1/+1
| | | | https://github.com/rubygems/rubygems/commit/06faad1e05
* [rubygems/rubygems] Extract matcher for slow perf specDavid Rodríguez2022-10-182-7/+13
| | | | https://github.com/rubygems/rubygems/commit/1c0eb63c6a
* [rubygems/rubygems] Simplify SpecGroup creationDavid Rodríguez2022-10-181-1/+1
| | | | https://github.com/rubygems/rubygems/commit/788e46e152
* thread_sync.c: Clarify and document the behavior of timeout == 0Jean Boussier2022-10-172-1/+14
| | | | | | | | | | | [Feature #18982] Instead of introducing an `exception: false` argument to have `non_block` return nil rather than raise, we can clearly document that a timeout of 0 immediately returns. The code is refactored a bit to avoid doing a time calculation in such case.
* Skip utime example with Intel C Compiler suiteHiroshi SHIBATA2022-10-131-5/+9
|
* Ignore excessive precisionsNobuyoshi Nakada2022-10-103-3/+3
|
* Add spec for `Coverage.supported?` and `start(eval: true)`. (#6499)Samuel Williams2022-10-081-5/+25
| | | * Don't emit coverage for eval when eval coverage is disabled.
* Add IO#timeout attribute and use it for blocking IO operations. (#5653)Samuel Williams2022-10-071-1/+9
|
* Introduce `Fiber.blocking{}` for bypassing the fiber scheduler. (#6498)Samuel Williams2022-10-061-0/+17
|
* [rubygems/rubygems] Fix little UI issue when bundler shows duplicated gems ↵David Rodríguez2022-10-061-0/+18
| | | | | | in a list https://github.com/rubygems/rubygems/commit/3f71d882e9
* [rubygems/rubygems] Make sure RSpec diffs don't omit the different partDavid Rodríguez2022-10-041-0/+2
| | | | | | | | | | | We sometimes check assertions on lockfile contents, which involves comparing a reasonably long string. Sometimes RSpec is not able to show the part of the string that's actually different, making it hard to figure out the issue. Configuring this setting should fix the issue in most cases. https://github.com/rubygems/rubygems/commit/5ad8ee499e
* [rubygems/rubygems] Copy template contents instead of file and permsVictor Gama2022-10-032-0/+27
| | | | | | | | | This allows the file to be created without copying permissions from Bundler's installation source. The previous behaviour was noticed after installing Ruby through brew, and using bundle init, which yielded a read-only Gemfile. https://github.com/rubygems/rubygems/commit/839a06851d
* Add Data class implementation: Simple immutable value objectVictor Shepelev2022-09-301-1/+13
|
* Add specs for {Method,UnboundMethod}#owner of a zsuper methodBenoit Daloze2022-09-292-0/+13
|
* Fix {Method,UnboundMethod}#super_method for zsuper methodsBenoit Daloze2022-09-292-22/+9
| | | | | * We need to resolve the zsuper method first, and then look the super method of that.
* Skip unpack_sockaddr_in with http at Solaris platformHiroshi SHIBATA2022-09-291-3/+5
| | | | http://rubyci.s3.amazonaws.com/solaris10-gcc/ruby-master/log/20220929T050003Z.fail.html.gz
* Update to ruby/spec@1d9d5c6Benoit Daloze2022-09-2851-259/+1142
|
* Update to ruby/mspec@b60306dBenoit Daloze2022-09-285-27/+11
|
* This commit implements the Object Shapes technique in CRuby.Jemma Issroff2022-09-281-9/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Object Shapes is used for accessing instance variables and representing the "frozenness" of objects. Object instances have a "shape" and the shape represents some attributes of the object (currently which instance variables are set and the "frozenness"). Shapes form a tree data structure, and when a new instance variable is set on an object, that object "transitions" to a new shape in the shape tree. Each shape has an ID that is used for caching. The shape structure is independent of class, so objects of different types can have the same shape. For example: ```ruby class Foo def initialize # Starts with shape id 0 @a = 1 # transitions to shape id 1 @b = 1 # transitions to shape id 2 end end class Bar def initialize # Starts with shape id 0 @a = 1 # transitions to shape id 1 @b = 1 # transitions to shape id 2 end end foo = Foo.new # `foo` has shape id 2 bar = Bar.new # `bar` has shape id 2 ``` Both `foo` and `bar` instances have the same shape because they both set instance variables of the same name in the same order. This technique can help to improve inline cache hits as well as generate more efficient machine code in JIT compilers. This commit also adds some methods for debugging shapes on objects. See `RubyVM::Shape` for more details. For more context on Object Shapes, see [Feature: #18776] Co-Authored-By: Aaron Patterson <tenderlove@ruby-lang.org> Co-Authored-By: Eileen M. Uchitelle <eileencodes@gmail.com> Co-Authored-By: John Hawthorn <john@hawthorn.email>
* Re-enable TZ test missed due to merge conflict.Vít Ondruch2022-09-271-2/+0
| | | | | | This was disabled by b7577b4d9e, while properly fixed upstream by: https://github.com/ruby/spec/pull/939
* Revert this until we can figure out WB issues or remove shapes from GCAaron Patterson2022-09-262-3/+10
| | | | | | | | | | Revert "* expand tabs. [ci skip]" This reverts commit 830b5b5c351c5c6efa5ad461ae4ec5085e5f0275. Revert "This commit implements the Object Shapes technique in CRuby." This reverts commit 9ddfd2ca004d1952be79cf1b84c52c79a55978f4.
* This commit implements the Object Shapes technique in CRuby.Jemma Issroff2022-09-262-10/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Object Shapes is used for accessing instance variables and representing the "frozenness" of objects. Object instances have a "shape" and the shape represents some attributes of the object (currently which instance variables are set and the "frozenness"). Shapes form a tree data structure, and when a new instance variable is set on an object, that object "transitions" to a new shape in the shape tree. Each shape has an ID that is used for caching. The shape structure is independent of class, so objects of different types can have the same shape. For example: ```ruby class Foo def initialize # Starts with shape id 0 @a = 1 # transitions to shape id 1 @b = 1 # transitions to shape id 2 end end class Bar def initialize # Starts with shape id 0 @a = 1 # transitions to shape id 1 @b = 1 # transitions to shape id 2 end end foo = Foo.new # `foo` has shape id 2 bar = Bar.new # `bar` has shape id 2 ``` Both `foo` and `bar` instances have the same shape because they both set instance variables of the same name in the same order. This technique can help to improve inline cache hits as well as generate more efficient machine code in JIT compilers. This commit also adds some methods for debugging shapes on objects. See `RubyVM::Shape` for more details. For more context on Object Shapes, see [Feature: #18776] Co-Authored-By: Aaron Patterson <tenderlove@ruby-lang.org> Co-Authored-By: Eileen M. Uchitelle <eileencodes@gmail.com> Co-Authored-By: John Hawthorn <john@hawthorn.email>
* Support using at toplevel in wrapped scriptChris Salzberg2022-09-244-0/+31
| | | | | | | Allow refinements to be used at the toplevel within a script that is loaded under a module. Fixes [Bug #18960]
* Enable coverage for eval.Samuel Williams2022-09-221-9/+25
|
* Rescue File.expand_path in MSpecScript#try_load if HOME is unavailableYuta Saito2022-09-211-1/+6
| | | | | | mspec tries to load ~/.mspecrc, but some platforms (e.g. WASI) doesn't have HOME concept, so `~` cannot be expanded and `File.expand_path` can fail.
* Remove warning for old TLS version connectionNobuyoshi Nakada2022-09-151-77/+0
| | | | | RubyGems.org already has refused connection requests using older than TLS 1.2.
* Deprecate Encoding#replicateBenoit Daloze2022-09-101-50/+58
| | | | * See [Feature #18949].
* [rubygems/rubygems] Fix unused variable warningDavid Rodríguez2022-09-081-2/+0
| | | | https://github.com/rubygems/rubygems/commit/ca8d47e53a
* Resync Bundler & RubyGemsDavid Rodríguez2022-09-0812-54/+160
|
* [rubygems/rubygems] Fix `set` not being found when running specs on dev rubiesDavid Rodríguez2022-09-061-0/+3
| | | | https://github.com/rubygems/rubygems/commit/c5b2960388
* [rubygems/rubygems] Add `syntax_suggest` to exemption list in setup specsDavid Rodríguez2022-09-061-0/+1
| | | | https://github.com/rubygems/rubygems/commit/f9a51e4380
* [rubygems/rubygems] Remove no longer needed `fiddle` hacksDavid Rodríguez2022-09-054-13/+0
| | | | | | | RubyInstaller has released patch versions backporting their changes to not load `fiddle` on boot, so all these are no longer necessary. https://github.com/rubygems/rubygems/commit/05a307deb2
* Merge ↵Hiroshi SHIBATA2022-09-0516-467/+130
| | | | https://github.com/rubygems/rubygems/commit/16c3535413afebcdbab7582c6017c27b5da8a8dc
* [rubygems/rubygems] Feature: `bundle add` supports `--path` optionMike Dalessio2022-09-051-0/+9
| | | | https://github.com/rubygems/rubygems/commit/32bee01fbe
* [rubygems/rubygems] Fix resolution hanging on musl platformsDavid Rodríguez2022-09-052-6/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | After recent musl support was added, Bundler started hanging in musl platforms. I identified the issue where valid candidates were being filtered out because their platform was specified as a string, and thus `Gem::Platform.match_spec?` which under the hood ends up calling `Gem::Platform#===` would return `nil`, because it does not support comparing platforms to strings. In particular, `Bundler::EndpointSpecification`'s platform coming from the API was not instantiated as a `Gem::Platform`, hence the issue. Also, this spec surfaced another issue where a bug corrected in `Gem::Platform#match_platforms` had not been yet backported to Bundler. So this commit also backports that to get the spec green across RubyGems versions. Finally, the fix in `Bundler::EndpointSpecification` made a realworld spec start failing. This spec was faking out `rails-4.2.7.1` requirement on Bundler in the `Gemfile.lock` file to be `>= 1.17, < 3` when the real requirement is `>= 1.17, < 2`. Due to the bug in `Bundler::EndpointSpecification`, the real requirement provided by the compact index API (recorded with VCR) was being ignored, and the `Gemfile.lock` fake requirement was being used, which made the spec pass. This is all expected, and to fix the issue I changed the spec to be really realworld and don't fake any Bundler requirements. https://github.com/rubygems/rubygems/commit/faf4ef46bc
* rb_int_range_last: properly handle non-exclusive rangeJean Boussier2022-09-041-0/+6
| | | | [Bug #18994]
* * append newline at EOF. [ci skip]git2022-09-021-1/+1
|
* Added doc about `test-syntax-suggest`Hiroshi SHIBATA2022-09-021-0/+12
|
* Added entries about test-bundler-parallel and BUNDLER_SPECSHiroshi SHIBATA2022-09-021-0/+8
|
* Skip a couple of chroot spec failluresTakashi Kokubun2022-08-291-2/+5
| | | | | I don't come up with a way to fix it right away. We'd need some experiments on a pull request.
* Update to ruby/spec@b8a8240Benoit Daloze2022-08-294-7/+8
|
* Update to ruby/mspec@37151a0Benoit Daloze2022-08-291-1/+2
|
* Update to ruby/spec@d01709fBenoit Daloze2022-08-2932-52/+473
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-07 20:28:50 +0000