| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* These seem to consistenly pass already
* Show actual command when running `make test-bundler`
Current the setup command that installs the necessary gems for testing
bundler was printed, but not the actual command that runs the tests.
That was a bit confusing.
* Borrow trick from setproctitle specs
* A title that long doesn't get set sometimes
No idea why, but the test doesn't need that the title is that long.
* Fix most gem helper spec ruby-core failures
* Fix the rest of the gem helper failures
* Fix version spec by improving the assertion
* Remove unnecessary `BUNDLE_RUBY` environment var
We can use `RUBY` when necessary, and `BUNDLE_RUBY` is not a good name
because bundler considers `BUNDLE_*` variables as settings.
* Rename `BUNDLE_GEM` to `GEM_COMMAND`
This is more descriptive I think, and also friendlier for bundler
because `BUNDLE_` env variables are interpreted by bundler as settings,
and this is not a bundler setting.
This fixes one bundler spec failure in config specs against ruby-core.
* Fix quality spec when run in core
Use the proper path helper.
* Fix dummy lib builder to never load default gems
If a dummy library is named as a default gem, when requiring the library
from its executable, the default gem would be loaded when running from
core, because in core all default gems share path with bundler, and thus
they are always in the $LOAD_PATH. We fix the issue by loading lib
relatively inside dummy lib executables.
* More exact assertions
Sometimes I have the problem that I do some "print debugging" inside
specs, and suddently the spec passes. This happens when the assertion is
too relaxed, and the things I print make it match, specially when they
are simple strings like "1.0" than can be easily be part of gem paths
that I print for debugging.
I fix this by making a more exact assertion.
* Detect the correct shebang when ENV["RUBY"] is set
* Relax assertion
So that the spec passes even if another paths containing "ext" are in
the load path. This works to fix a ruby-core issue, but it's a better
assertion in general. We just want to know that the extension path was
added.
* Use folder structure independent path helper
It should fix this spec for ruby-core.
* Fix the last failing spec on ruby-core
* Skip `bundle open <default_gem>` spec when no default gems
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
For debuggability.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
ruby < 2.6"
This reverts commit e63e844bc7444c6a489fcde0dc7011c6c4807edd.
It was introduced to resolve some failing tests at the cost of making
the intention of the spec much less clear.
Thanks to the previous fixes we have added to this spec, we can revert
that patch now.
|
| |
|
|
|
|
| |
Gem::ConfigMap is compatibility code for the old Ruby like 1.8/1.9.
|
|
|
|
|
|
|
|
|
|
|
| |
Windows paths do not start with a slash, so we add an extra slash to
separate the host from the path in file:// urls. Otherwise "D:" is
parsed as the host segment in the URI.
The path for those URLs now starts with "/", so we ignore that leading
character when using the URI's path.
This reduces Windows CI spec failures from 429 to 355.
|
| |
|
|
|
|
|
|
| |
* Drop bundler 1 stuff from tests.
* Move all feature flags to bundler 3 (like they are in 2-0-stable) and
get them tested.
|
|
|
|
| |
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66993 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
| |
|
|
|
|
|
| |
* To use libexec instead of bin directory.
* Restore exe direcotry for bundler.gemspec while running test suite.
|
| |
|
| |
|
|
|
|
| |
They are replaced build binary on ruby core repository.
|
|
|
|
|
|
|
|
| |
@segiddins encouraged contributions towards support for Windows
https://github.com/bundler/bundler/issues/5992#issuecomment-326809543
As a first step towards this goal this commit fixes file path specification
in the first pieces of Ruby code called when setting up a test environment.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Ruby core needs to change `Spec::Path.root` and gemspec, bin, spec
directories structure.
* Added Spec::Path.bin, gemspec, spec methods.
* Replace Spec::Path methods from relative references like "../../..".
|
| |
|
| |
|
|
|
|
|
| |
This was, modifications to the temporary directory are blown away
between each test and don't clutter the user's FS
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
resolve when then shouldn't
|
|
|
|
|
|
| |
This PR adds a general purpose Retry class that can be re-used where-ever retry code is needed!
It also allows you to call `bundle install --retry 3` which will attempt to connect to ruby gems 3 times before failing, and emit a warning message each time
|
| |
|
| |
|
|
|
|
|
|
| |
* Note that signed certs with a CA are untested. Hopefully they are
tested appropriately at the rubygems level.
* update is tested via config entry
|
| |
|
|
|
|
|
| |
* vendored_gems should be vendor/bundle
* bundle install <path> is deprecated, use bundle install --path <path>
|
|
|
|
|
|
|
|
| |
Pathname.join do not properly respect quoted paths. Path with spaces
still fails since quotes around every -I and path expressed is required.
Removing this since a long term solution must achieved instead of this
short-term and failed scenario.
|
| |
|
| |
|
| |
|