summaryrefslogtreecommitdiff
path: root/test/rubygems
AgeCommit message (Collapse)Author
2020-02-13test/rubygems/test_gem_commands_setup_command.rb: Allow /bin/envYusuke Endoh
Follow up of 65201c054a90c8e7beb8fe1e6d0006541ac33449
2020-02-12test/rubygems: Try not only /usr/bin/env but also /bin/envYusuke Endoh
RubyGems chooses available one from the two https://github.com/rubygems/rubygems/blob/20b0d609484df2b514954ba9ef890a7cbdd01d18/lib/rubygems/installer.rb#L38 So, it is good not to hard-code /usr/bin/env in tests.
2020-02-06Revert "[rubygems/rubygems] Fix require issue with file extension priority"Hiroshi SHIBATA
This reverts commit d767da428c28b7b9fec56b383bb32f6f76c6ad26. It fails with spec/ruby/core/kernel/require_spec.rb:5
2020-02-06Revert to remove the query command of rubygems.Hiroshi SHIBATA
The original commit was https://github.com/rubygems/rubygems/pull/3119
2020-02-06[rubygems/rubygems] Fix require issue with file extension priorityDavid Rodríguez
If `require "a"` is run when two folders have been specified in the -I option including a "a.rb" file and a "a.so" file respectively, the ruby spec says that the ".rb" file should always be preferred. However, the logic we added in https://github.com/rubygems/rubygems/commit/6b81076d9 to make the -I option always beat default gems does not respect this spec, creating a difference from the original ruby-core's require. [the ruby spec says]: https://github.com/ruby/spec/blob/d80a6e2b221d4f17a8cadcac75ef950c59cba901/core/kernel/shared/require.rb#L234-L246 https://github.com/rubygems/rubygems/commit/b3944384f4
2020-02-06[rubygems/rubygems] Make non "test_" method privateDavid Rodríguez
https://github.com/rubygems/rubygems/commit/912d141a35
2020-02-03test/rubygems/test_gem_remote_fetcher.rb: Remove a duplicated testYusuke Endoh
https://rubyci.org/logs/rubyci.s3.amazonaws.com/ubuntu1604/ruby-master/log/20200203T003005Z.log.html.gz ``` /home/hsbt/chkbuild/tmp/build/20200203T003005Z/ruby/test/rubygems/test_gem_remote_fetcher.rb:485: warning: method redefined; discarding old test_fetch_path_socket_error /home/hsbt/chkbuild/tmp/build/20200203T003005Z/ruby/test/rubygems/test_gem_remote_fetcher.rb:167: warning: previous definition of test_fetch_path_socket_error was here ```
2020-02-01Merge the current master branch of rubygems/rubygems.Hiroshi SHIBATA
Just started to develop RubyGems 3.2.0.
2020-01-02Update tests for full keyword argument separationJeremy Evans
Notes: Merged: https://github.com/ruby/ruby/pull/2794
2019-12-20Merge RubyGems 3.1.2Hiroshi SHIBATA
2019-12-15Prepare to release rubygems-3.1.0Hiroshi SHIBATA
2019-12-13Fixed a typoHiroshi SHIBATA
2019-12-13Added explicitly loading `Gem::Command` classHiroshi SHIBATA
2019-12-13Prepare to release RubyGems 3.1.0 final version.Hiroshi SHIBATA
2019-12-11Do not load q.rb in build directoryKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2736
2019-12-11Do not load files in build directoryKazuhiro NISHIYAMA
related https://bugs.ruby-lang.org/issues/16177 Notes: Merged: https://github.com/ruby/ruby/pull/2736
2019-11-11Merge RubyGems 3.1.0.pre3Hiroshi SHIBATA
* Fix gem pristine not accounting for user installed gems. Pull request #2914 by Luis Sagastume. * Refactor keyword argument test for Ruby 2.7. Pull request #2947 by SHIBATA Hiroshi. * Fix errors at frozen Gem::Version. Pull request #2949 by Nobuyoshi Nakada. * Remove taint usage on Ruby 2.7+. Pull request #2951 by Jeremy Evans. * Check Manifest.txt is up to date. Pull request #2953 by David Rodríguez. * Clarify symlink conditionals in tests. Pull request #2962 by David Rodríguez. * Update command line parsing to work under ps. Pull request #2966 by David Rodríguez. * Properly test `Gem::Specifications.stub_for`. Pull request #2970 by David Rodríguez. * Fix Gem::LOADED_SPECS_MUTEX handling for recursive locking. Pull request #2985 by MSP-Greg. Notes: Merged: https://github.com/ruby/ruby/pull/2666
2019-11-11Remove binary data at installationNobuyoshi Nakada
And revert "Relaxed warning assertions", 6f9be8505d172b110ec449478a791d70b9b74afb.
2019-11-11Relaxed warning assertionsNobuyoshi Nakada
2019-10-29test/rubygems/test_gem.rb: early failure when there is /tmp/GemfileYusuke Endoh
Some test cases in rubygems assume that /tmp/Gemfile does not exist. If it does, they fail with very difficult-to-understand message: ``` [ 149/2108] TestGemBundlerVersionFinder#test_bundler_version_with_bundle_update_bundler = 0.00 1) Failure: TestGemBundlerVersionFinder#test_bundler_version_with_bundle_update_bundler [/home/mame/work/ruby/test/rubygems/test_gem_bundler_version_finder.rb:38]: Expected Gem::Version.new("2.0.2") to be nil. ``` I spent one hour to debug this issue. To prevent the same accident, this change makes the test suite stop when /tmp/Gemfile explicitly.
2019-10-15[rubygems/rubygems] Also bump test variableHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/97e9768612
2019-10-10[rubygems/rubygems] Do not compare with unreliable Gem::Specification::TODAYNobuyoshi Nakada
https://gist.github.com/ko1/a88834d744a0682711dab53fd9015a04#file-brlog-trunk-nopara-20191005-235153-L393-L472 https://github.com/rubygems/rubygems/commit/707408d8e7
2019-10-10[rubygems/rubygems] Restrict possible date rangeNobuyoshi Nakada
https://github.com/rubygems/rubygems/commit/1bd77f53df
2019-10-05Now keyword parameter warnings are suppressed by 871005bdd204Nobuyoshi Nakada
This reverts commits: * 2a490d5660ac869f8f2bbcec4887b1dc2950643f Suppress assert_match warnings. * d4a86e407ec2057c2c7ad757aa76dad757f34c3a Assert warnings message for the last argument is keyword parameter.
2019-10-05[rubygems/rubygems] The date might have advanced since TODAY has been setNobuyoshi Nakada
https://bugs.ruby-lang.org/issues/16189 https://github.com/rubygems/rubygems/commit/e331222163
2019-10-05[rubygems/rubygems] Add Gem::Dependency#identity methodbronzdoc
https://github.com/rubygems/rubygems/commit/05146bb2fd
2019-10-05[rubygems/rubygems] Suppress keywords warning in ruby 2.7Nobuyoshi Nakada
https://github.com/rubygems/rubygems/commit/892bfc11fe
2019-10-05[rubygems/rubygems] Use dedicated assertion methodsNobuyoshi Nakada
For better messages at failures. https://github.com/rubygems/rubygems/commit/971455b16e
2019-10-05[rubygems/rubygems] Fixed assertion argumentsNobuyoshi Nakada
It is `assert_eqal(expected, actual)`. https://github.com/rubygems/rubygems/commit/1d6197a090
2019-09-26Suppress assert_match warnings.Hiroshi SHIBATA
2019-09-26Assert warnings message for the last argument is keyword parameter.Hiroshi SHIBATA
2019-09-26[rubygems/rubygems] Make sure our modifications to kernel.warn workDavid Rodríguez
And test the fix we're adding. https://github.com/rubygems/rubygems/commit/6f86637b98
2019-09-26[rubygems/rubygems] indentHiroshi SHIBATA
https://github.com/rubygems/rubygems/commit/8cdb2fd66f
2019-09-26[rubygems/rubygems] Fix test_gem_attrbronzdoc
https://github.com/rubygems/rubygems/commit/7c5b66f9ef
2019-09-26[rubygems/rubygems] add testsf
https://github.com/rubygems/rubygems/commit/8a7e27381c
2019-09-26[rubygems/rubygems] Fix underscore version for bundler itselfDavid Rodríguez
Previously it wouldn't play nice with the bundler version finder. https://github.com/rubygems/rubygems/commit/d8bb81556d
2019-09-26[rubygems/rubygems] Update expectation in test_to_ruby_with_rsa_keybronzdoc
https://github.com/rubygems/rubygems/commit/2e65f7d4ae
2019-09-26[rubygems/rubygems] Make ruby_code method handle OpenSSL::PKey::RSA objectsbronzdoc
https://github.com/rubygems/rubygems/commit/b1d825ab3a
2019-09-26[rubygems/rubygems] Set SOURCE_DATE_EPOCH env var if not provided.Ellen Marie Dash
Fixes #2290. 1. `Gem::Specification.date` returns SOURCE_DATE_EPOCH when defined, 2. this commit makes RubyGems set it _persistently_ when not provided. This combination means that you can build a gem, check the build time, and use that value to generate a new build -- and then verify they're the same. https://github.com/rubygems/rubygems/commit/d830d53f59
2019-09-26[rubygems/rubygems] Add a gem attr to the Gem::Package class.Daniel Berger
https://github.com/rubygems/rubygems/commit/5b81f364ae
2019-09-05[rubygems/rubygems] Bump rubocop to 0.74.0 and fix new offensesDavid Rodríguez
https://github.com/rubygems/rubygems/commit/d4fc383497
2019-09-05[rubygems/rubygems] Fix Layout/SpaceAroundOperators: Operator = should be ↵bronzdoc
surrounded by a single space. https://github.com/rubygems/rubygems/commit/eaa38ebeb1
2019-09-05[rubygems/rubygems] Error out if there are multiple gemspecs and no gemspec ↵bronzdoc
is specified https://github.com/rubygems/rubygems/commit/547947bbf0
2019-09-05[rubygems/rubygems] Remove useless gem setupbronzdoc
https://github.com/rubygems/rubygems/commit/c8913e37a7
2019-09-05[rubygems/rubygems] Test building a gem with multiple gemspec without a gem ↵bronzdoc
name specified https://github.com/rubygems/rubygems/commit/38c72fd145
2019-09-05[rubygems/rubygems] Build the first gemspec we found if no gemspec is specifiedbronzdoc
https://github.com/rubygems/rubygems/commit/ab186266b7
2019-09-05[rubygems/rubygems] Improve gemspec assignment and error messagebronzdoc
https://github.com/rubygems/rubygems/commit/dc70c5a192
2019-09-05[rubygems/rubygems] Don't fail when `uninstall --all` with default gemDavid Rodríguez
Instead, display an informative message saying that uninstallation of specific versions is being skipped because of being default gems. https://github.com/rubygems/rubygems/commit/b44845aa1d
2019-09-05[rubygems/rubygems] Little refactor to avoid rubocop's false positiveDavid Rodríguez
Otherwise it detects duplicate methods here, because it doesn't see that we are reopening the class in two different places. https://github.com/rubygems/rubygems/commit/ae3fb47f5f
2019-08-17Skip teardown with JRubyHiroshi SHIBATA
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-19 05:49:28 +0000