summaryrefslogtreecommitdiff
path: root/spec
AgeCommit message (Collapse)Author
2021-10-22Refinement#include and Refinement#prepend have been deprecatedNobuyoshi Nakada
2021-10-22Refinement#include and Refinement#prepend have been deprecatedNobuyoshi Nakada
2021-10-20Fix tests with cppflags=-DYJIT_FORCE_ENABLETakashi Kokubun
https://github.com/ko1/build-ruby/commit/0dbd95c6250594b6ddadc3c4424b071704083187
2021-10-20Update to ruby/spec@254c380Benoit Daloze
2021-10-20Add extra files from ruby/spec which were skipped due to .gitignoreBenoit Daloze
2021-10-20Update to ruby/spec@d6921efBenoit Daloze
2021-10-20Update to ruby/mspec@08e1275Benoit Daloze
2021-10-18Fix error when srcdir not foundNobuyoshi Nakada
So that `spec/mspec/bin/mspec --help` works at least.
2021-10-18Simplify srcdir fallbackNobuyoshi Nakada
2021-10-18Not all environment variables can be convertible to IBM-437Nobuyoshi Nakada
2021-10-13[rubygems/rubygems] Improve error messages in gem helpersDavid Rodríguez
Previously they were printing the original command that was run, and telling the user to rerun it. However, the command sometimes would not match the exact command that was run (for example, when using the `--local` flag), and in any case, it's simpler and more useful to print the underlying error anyways. https://github.com/rubygems/rubygems/commit/5bc0d51b58
2021-10-13[rubygems/rubygems] Fix `bundle install` crash due to an incorrectly ↵David Rodríguez
incomplete resolve In case we have a corrupted lockfile that claims to support a platform, but it's missing platform specific gems for it, bundler has a check that detects the situation and forces a re-resolve. The result of this check is kept under the `@locked_specs_incomplete_for_platformn` instance variable in `Definition`. The installer, however, calls `Definition#nothing_changed?` before this instance variable has been filled, so the result of it is actually incorrect here since it will claim that nothing has changed, but something has changed (locked specs are incomplete for the current platform). The consequence of this incorrect result is that the installer thinks it can go on without re-resolving, resulting in the incomplete resolution from the lockfile being used, and in a crash being triggered due to that. The solution is to make sure the `@locked_specs_incomplete_for_platform` instance variable is filled before `nothing_changed?` gets called. Moving it to `initialize` makes the most sense, not because it's the best place for it (we can refactor this later), but because all of the other "outdated definition" checks are already set there. https://github.com/rubygems/rubygems/commit/708afdd789
2021-10-13[rubygems/rubygems] Fix `bundle install` to force reinstallation of deleted gemsDavid Rodriguez
https://github.com/rubygems/rubygems/commit/8950631f02
2021-10-13[rubygems/rubygems] Use correct way to detect default gemsDavid Rodríguez
The other way, in particular matching a substring in the gemspec summary, is brittle and no longer used since Ruby 2.0. This needed rewriting the specs that depended on that way. https://github.com/rubygems/rubygems/commit/059dbfa971
2021-10-13[rubygems/rubygems] Remove unnecessary codeDavid Rodríguez
All supported rubygems versions implement this. https://github.com/rubygems/rubygems/commit/2130782ef6
2021-10-13[rubygems/rubygems] Make spec more realisticDavid Rodriguez
The spec was just faking an installed gemspec without any installed gem backing it up, resulting in `bundle install` claiming that the gem was already installed when it was not. https://github.com/rubygems/rubygems/commit/c35531d1c7
2021-10-13Fix a typoKazuhiro NISHIYAMA
2021-10-11[rubygems/rubygems] Show a warning in `bundle info` if gem has been deletedDavid Rodriguez
https://github.com/rubygems/rubygems/commit/ff86cd7dd2
2021-10-11[rubygems/rubygems] Show the exact name of the gem that was deletedDavid Rodriguez
If a non exact name (matched as a regexp) is passed to `bundle info`, these strings might not match. https://github.com/rubygems/rubygems/commit/831edf1edf
2021-10-11[rubygems/rubygems] Match a more exact warning messageDavid Rodriguez
https://github.com/rubygems/rubygems/commit/80158e9d75
2021-10-11[ruby/rubygems] Get specs green on arm64-darwin-20David Rodriguez
https://github.com/rubygems/rubygems/commit/7a0bd9801d
2021-10-10Use an isolated classNobuyoshi Nakada
The number of all instances of `Class` may be affected by GC-able anonymous classes created by other tests.
2021-10-09Newly generated gems require Ruby 2.6.0OKURA Masafumi
In 2021, Ruby 2.5 and older are EOL. We can set the default required Ruby version to 2.6.0 to encourage people to use newer Ruby. If the command is executed with old Ruby, it falls back to 2.3.0. It's still possible to create a gem for older Ruby just by changing two lines of code (one in gemspec and another is in rubocop.yml).
2021-10-09[rubygems/rubygems] I see no harm in this, allow itDavid Rodríguez
https://github.com/rubygems/rubygems/commit/01feb40283
2021-10-09[rubygems/rubygems] `git commit` no longer needs to be allowed to failDavid Rodríguez
https://github.com/rubygems/rubygems/commit/12af03d32f
2021-10-09[rubygems/rubygems] Let `update_git` work with whatever branch is checkout outDavid Rodríguez
Unless the `:branch` option is passed. It's more efficient, and it results in less hardcoding of "master". https://github.com/rubygems/rubygems/commit/aa5c3409ab
2021-10-09[rubygems/rubygems] Make adding files and committing into a single commandDavid Rodríguez
For efficiency. https://github.com/rubygems/rubygems/commit/979d1634dd
2021-10-09[rubygems/rubygems] Keep different code in custom branch in dummy repoDavid Rodríguez
This doesn't affect the outcome of the test, but it makes the `git commit` command inside `update_git` not fail because of not having anything to commit. https://github.com/rubygems/rubygems/commit/ad0160ed97
2021-10-09[rubygems/rubygems] Fix typoDavid Rodríguez
We want to update the original repo, not a fresh one. This went undetected because the `git commit` command inside the `update_git` method ignores failures, and in this case it was failing because all files are untracked in the new repo. I will fix that later but for now fix the typo. https://github.com/rubygems/rubygems/commit/c889f1d715
2021-10-09[rubygems/rubygems] Improve performance of Specification#missing_extensions?Masataka Pocke Kuwabara
https://github.com/rubygems/rubygems/commit/90c1919f94
2021-10-09[rubygems/rubygems] Add glob infomation to Bundler::Source::Git#to_sgabriele renzi
The glob information was not specified in the string representation for a source, which led to non-deterministic behaviour when generating the lockfile, since sources are sorted by this value. https://github.com/rubygems/rubygems/commit/493b880abc
2021-10-08Remove autoload for constant if the autoload failsJeremy Evans
Previously, if an autoload failed (the file was loaded, but the constant was not defined by the autoloaded file). Ruby will try to autoload again if you delete the autoloaded file from $LOADED_FEATURES. With this change, the autoload and the constant itself are removed as soon as it fails. To handle cases where multiple threads are autoloading, when deleting an autoload, handle the case where another thread already deleted it. Fixes [Bug #15790] Notes: Merged: https://github.com/ruby/ruby/pull/4715 Merged-By: jeremyevans <code@jeremyevans.net>
2021-10-07Followed up bd6e1a0f0883dba7b02f30cefe5ebec96d02cb90Hiroshi SHIBATA
2021-10-06Remove the useless platform guardNobuyoshi Nakada
2021-10-06Fix filesystem dependent testsNobuyoshi Nakada
Ruby cannot guarantee the resolutions of underlying filesystems.
2021-10-05Update to ruby/spec@ccf0d85Benoit Daloze
2021-10-05marshal.c Marshal.load accepts a freeze: true option.Jean Boussier
Fixes [Feature #18148] When set, all the loaded objects are returned as frozen. If a proc is provided, it is called with the objects already frozen.
2021-09-30marshal.c: don't call the proc with partially initialized objects. (#4866)Jean byroot Boussier
For cyclic objects, it requires to keep a st_table of the partially initialized objects. Notes: Merged-By: byroot <jean.boussier@gmail.com>
2021-09-28Followed up behavior change of setHiroshi SHIBATA
https://github.com/ruby/ruby/commit/f360ebb30606a4143029996073d29d007069428d
2021-09-28Followed up ruby/spec examples for date.Hiroshi SHIBATA
https://github.com/ruby/ruby/commit/f9f7f3a75ec5af4a70e3332f8f5aa300c13432e2
2021-09-25FL_USER flags on ohter than T_DATA are reserved [Misc #18059]Nobuyoshi Nakada
2021-09-24FL_USER flags on ohter than T_DATA are reserved [Misc #18059]Nobuyoshi Nakada
2021-09-22[rubygems/rubygems] Fix possible malicious website to example.comfiveNinePlusR
example.com is the canonical stand in for domain examples and will never have a backing website. via https://www.rfc-editor.org/rfc/rfc2606.html https://github.com/rubygems/rubygems/commit/26622c81c2
2021-09-20Don't describe C function that does not exist in prior versions.Samuel Williams
Notes: Merged: https://github.com/ruby/ruby/pull/4871
2021-09-20Add C interface spec.Samuel Williams
Notes: Merged: https://github.com/ruby/ruby/pull/4649
2021-09-17[rubygems/rubygems] Trigger install command by default on removeJose Galisteo
Closes https://github.com/rubygems/rubygems/issues/4889 https://github.com/rubygems/rubygems/commit/2b1754479c
2021-09-17Removed Module.allocate [Bug #17048]Nobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/4858
2021-09-17Add spec for MatchData#match and MatchData#match_length [Feature #18172]Nobuyoshi Nakada
2021-09-15Marshal.load: do not call the proc until strings have their encodingJean Boussier
Ref: https://bugs.ruby-lang.org/issues/18141 Notes: Merged: https://github.com/ruby/ruby/pull/4797
2021-09-12Add printf attribute to functions call va_list format functionsNobuyoshi Nakada
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-21 09:00:59 +0000