summaryrefslogtreecommitdiff
path: root/spec
AgeCommit message (Collapse)Author
2024-11-21Removed needless require for build_metadataHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12137
2024-11-21[rubygems/rubygems] Explicitly load build_metadata.rb because ↵Hiroshi SHIBATA
Spec::BuildMetadata is only called from BundlerBuilder. The current code is broken to call Spec::Builders#build_* method directly. https://github.com/rubygems/rubygems/commit/4922ae40dd
2024-11-21[rubygems/rubygems] Silent verbose stdout for dependency of test gemsHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/51854e1982
2024-11-20[rubygems/rubygems] Add man page for 'bundle issue' commandAndrew Nesbitt
https://github.com/rubygems/rubygems/commit/3f39571181
2024-11-19[rubygems/rubygems] Add man page for 'bundle fund' commandAndrew Nesbitt
Signed-off-by: Andrew Nesbitt <[email protected]> https://github.com/rubygems/rubygems/commit/897819da36
2024-11-19[rubygems/rubygems] Fix binstub test bugsodacris
the overwritten binstub in the test has a final new line that makes it not match "OMG" exactly from the beginning, that's why the test passes, but `bintubs` command without `--force` flag is not supposed to update the binstub. This change fixes the test to test what's supposed to update the binstub, and also fixes the assertion that that it will fail in the future if `--force` stops updating the binstub. https://github.com/rubygems/rubygems/commit/dfc9023337
2024-11-19[Bug #20900] Warn deprecated constant when removingNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/12114
2024-11-19Test with sinatra to 4.1.0David Rodríguez
2024-11-18Move configuration to RSpec.configureHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12111
2024-11-18Need to install all of dependency for bundler test suiteHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12111
2024-11-18Fixed required path with example locationHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12111
2024-11-18Load required helpers from bundler examples and invoke bundled_gems_spec.rb ↵Hiroshi SHIBATA
at test-bundled-gems Notes: Merged: https://github.com/ruby/ruby/pull/12111
2024-11-18Move spec directory from bundler examplesHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12111
2024-11-18Don't use Spec::Path.base_system_gem_pathHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12110
2024-11-15Port test_warn_zeitwerk.rb to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12098
2024-11-15Port test_warn_bootsnap_and_gem.rb to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12098
2024-11-15Port test_warn_bootsnap_rubyarchdir_gem.rb to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12098
2024-11-15Port test_warn_bootsnap.rb to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12098
2024-11-15Port test_no_warn_sub_feature.rb to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12096
2024-11-15Port test_warn_sub_feature.rb to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12096
2024-11-15Port -r option test to RSpec examplesHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12096
2024-11-15Port bundle exec with shebang script to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12096
2024-11-15Port bundle exec warning check to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12096
2024-11-15Port test_no_warn_dependency.rb to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12096
2024-11-15Port test_warn_dependency.rb to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12096
2024-11-15Port test_no_warn_dash_gem.rb to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12096
2024-11-15[ruby/syntax_suggest] Fix missing line break due to puts logicSchneems
In #225 it was reported that the output looks incorrect: ``` $ cat /tmp/4a71c7e417cc9eac0971e3a2519b295c/scratch.rb def x.y.z end $ ruby /tmp/4a71c7e417cc9eac0971e3a2519b295c/scratch.rb /tmp/4a71c7e417cc9eac0971e3a2519b295c/scratch.rb: --> /tmp/4a71c7e417cc9eac0971e3a2519b295c/scratch.rb expected a delimiter to close the parametersunexpected '.', ignoring it > 1 def x.y.z > 2 end ``` Specifically: ``` expected a delimiter to close the parametersunexpected '.', ignoring it ``` However this does not show up when executing the debug executable: ``` $ bin/bundle exec exe/syntax_suggest /tmp/4a71c7e417cc9eac0971e3a2519b295c/scratch.rb --> /tmp/4a71c7e417cc9eac0971e3a2519b295c/scratch.rb expected a delimiter to close the parameters unexpected '.', ignoring it > 1 def x.y.z > 2 end ``` This is because `exe/syntax_suggest` uses STDOUT.puts while calling `ruby` with the filename uses a fake IO object represented by MiniStringIO. This class was incorrectly not adding a newline to the end of the print. The fix was to move the class to it's own file where it can be tested and then fix the behavior. close https://github.com/ruby/syntax_suggest/pull/225 https://github.com/ruby/syntax_suggest/commit/d2ecd94a3b Co-authored-by: Andy Yong <[email protected]>
2024-11-15Use environmental variable for bundled_gems_spec.rbHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12086
2024-11-15Port test_warn_redefined.rb to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12086
2024-11-15Port test_warn_dash_gem.rb to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12086
2024-11-15Port test_warn_bundled_gems.rb to RSpec exampleHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/12086
2024-11-14Include the currently active GC in RUBY_DESCRIPTIONMatt Valentine-House
This will add +MOD_GC to the version string and Ruby description when Ruby is compiled with shared gc support. When shared GC support is compiled in and a GC module has been loaded using RUBY_GC_LIBRARY, the version string will include the name of the currently active GC as reported by the rb_gc_active_gc_name function in the form +MOD_GC[gc_name] [Feature #20794] Notes: Merged: https://github.com/ruby/ruby/pull/11872
2024-11-14[rubygems/rubygems] Revert "mustermann depends on URI::RFC2396_PARSER behavior"Hiroshi SHIBATA
This reverts commit https://github.com/rubygems/rubygems/commit/82b25dd75afd. https://github.com/rubygems/rubygems/commit/16adf53f23
2024-11-14[rubygems/rubygems] Fix `bin/rake spec:all` taskDavid Rodríguez
Only in CI, if two different test runs are started (like `bin/rake spec:all` does), the second one would not install the dev version of Bundler and would fail to start. This commit makes it work the same locally and in CI. https://github.com/rubygems/rubygems/commit/7a5ca6c40f
2024-11-14[rubygems/rubygems] I don't see how this could happenDavid Rodríguez
https://github.com/rubygems/rubygems/commit/8b6f9b7f05
2024-11-14[rubygems/rubygems] Make sure `bundle viz` specs are actually runDavid Rodríguez
These are marked as realworld, but the realworld workflow file does not install graphviz, so the specs are actually skipped. These are not actually realworld, so remove that tag. Now they'll be run together with the reset of specs in the standard workflow file, which does install `graphviz`. https://github.com/rubygems/rubygems/commit/e865fcaa22
2024-11-13Mark strings returned by Symbol#to_s as chilled (#12065)Jean byroot Boussier
* Use FL_USER0 for ELTS_SHARED This makes space in RString for two bits for chilled strings. * Mark strings returned by `Symbol#to_s` as chilled [Feature #20350] `STR_CHILLED` now spans on two user flags. If one bit is set it marks a chilled string literal, if it's the other it marks a `Symbol#to_s` chilled string. Since it's not possible, and doesn't make much sense to include debug info when `--debug-frozen-string-literal` is set, we can't include allocation source, but we can safely include the symbol name in the warning message, making it much easier to find the source of the issue. Co-Authored-By: Étienne Barrié <[email protected]> --------- Co-authored-by: Étienne Barrié <[email protected]> Co-authored-by: Jean Boussier <[email protected]>
2024-11-13[rubygems/rubygems] Include original error when openssl fails to loadDavid Rodríguez
https://github.com/rubygems/rubygems/commit/440343b791
2024-11-11[rubygems/rubygems] Add a `lockfile_checksums` configuration to include ↵David Rodríguez
checksums in fresh lockfiles https://github.com/rubygems/rubygems/commit/50b9ef8589
2024-11-11[rubygems/rubygems] Cancel `bundle console` deprecationDavid Rodríguez
https://github.com/rubygems/rubygems/commit/506a863b36
2024-11-08[rubygems/rubygems] Fix private registry credentials being written to logssamisalamiws
https://github.com/rubygems/rubygems/commit/d070fa10c1 Co-authored-by: Artem Ignatyev <[email protected]>
2024-11-08[rubygems/rubygems] Warn on insecure materializationDavid Rodríguez
https://github.com/rubygems/rubygems/commit/bc2537de71
2024-11-08[rubygems/rubygems] Fix typoDavid Rodríguez
https://github.com/rubygems/rubygems/commit/f68a2c30bb
2024-11-08[rubygems/rubygems] Simplify tests that deal with lockfile using only "ruby" ↵David Rodríguez
platform Using an old bundler version was necessary at the beginning because we checked the version of Bundler being run in order to enable the new behavior. But we removed that a long time ago and now we only look at whether the lockfile only includes "ruby" as a platform or not. https://github.com/rubygems/rubygems/commit/8fc3d38ff3
2024-11-08[rubygems/rubygems] Make sure platforms in spec lockfile are properly sortedDavid Rodríguez
https://github.com/rubygems/rubygems/commit/99b4ac4548
2024-11-08Do not round `a**b` to infinityYusuke Endoh
... instead, just calculate the value unless it is too big. Also, this change raises an ArgumentError if it is expected to exceed 16 GB in a 64-bit environment. (It is possible to calculate it straightforward, but it would likely be out-of-memory, so I didn't think it would make sense.) [Feature #20811] Notes: Merged: https://github.com/ruby/ruby/pull/12033
2024-11-08[rubygems/rubygems] Add `bundle lock --add-checksums` to add checksums to an ↵David Rodríguez
existing lockfile https://github.com/rubygems/rubygems/commit/0a9c1ce60d
2024-11-07Quarantine unreliable specBenoit Daloze
* See discussion on https://github.com/ruby/spec/pull/1210
2024-11-07[rubygems/rubygems] Undeprecate Gemfiles without a global sourceDavid Rodríguez
After having a second look at this deprecation, the explanation that we're giving does not make a lot of sense. When working only with local gems, Bundler will indeed generate a different lockfile depending on the latest installed version of each gem is at `bundle install` time. That's the same situation that happens with remote sources: Bundler will generate a different lockfile depending on the latest version of each gem available remotely. So, I don't think "a consistent lockfile not getting generated" is a good motivation for deprecating this. Also, this deprecation brings additional challenges, since for example, it should arguably not get printed when using `bundle install --local`? The original problem when this deprecation was introduced was an incorrect message about a missing gem having been yanked. So, I think a better solution is to, as long as we give proper error messages when things go wrong, let users do what's best for them and undo the deprecation. https://github.com/rubygems/rubygems/commit/17499cb83f
2024-11-07Loosen the criteria for timing checks of Kernel#sleepYusuke Endoh
The test was too flaky
generated by cgit v1.2.3 (git 2.25.1) at 2025-06-20 11:28:48 +0000