| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
| |
RubyGems 2.7 promote bundler-1.16 to default gems.
It conflicts Travis environment and user installed bundler.
|
|
|
|
| |
This reverts commit 6ec0ed67d9afcc666ad0424b10e9903f63e60714.
|
|
|
|
|
| |
JRuby 9.1.15.0 has been released:
http://jruby.org/2017/12/07/jruby-9-1-15-0.html
|
|
|
|
| |
These are needed when GEM=ast, thanks @georgeclaghorn
|
|
|
|
|
| |
JRuby 9.1.14.0 has been released and this version is available on Travis CI.
http://jruby.org/2017/11/08/jruby-9-1-14-0
|
|
|
|
|
|
|
|
|
|
| |
Since 8f2490b, the integration test of sidekiq and resque is not working
in CI.
https://travis-ci.org/rails/rails/jobs/301276197#L2055
https://travis-ci.org/rails/rails/jobs/301276197#L2061
Because 8f2490b removed password from `redis-server`.
So must also remove passwords from these tests.
|
|
|
|
|
|
|
|
| |
Simplify our dev testing and CI story since we're also testing against
Redis for the Active Support cache store.
Directly test whether db, host, password, etc are passed through as
config instead of spinning up a Redis server with a password set on it.
|
|
|
|
|
|
|
| |
This reverts commit 6f481e05bb24fe3589ef0f65e97a9b1fa66ae0f7, reversing
changes made to 592f790b7693c0a32cd06d5e8201639923a734c5.
In favor of #31039.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
when tested with ruby-head
This pull request attempts to ignore the following error
when tested with ruby-head which has bundler as a default gem.
```ruby
$ rvm @global do gem uninstall bundler --all --ignore-dependencies --executables
ERROR: While executing gem ... (Gem::InstallError)
gem "bundler" cannot be uninstalled because it is a default gem
The command "rvm @global do gem uninstall bundler --all --ignore-dependencies --executables" failed and exited with 1 during .
```
Refer https://travis-ci.org/rails/rails/jobs/295600391
This workaround should be removed once https://github.com/bundler/bundler/issues/6072 is addressed.
|
|
|
|
|
|
|
|
| |
Since 1.16.0 is installed by default, it seems that the newer one will be used
even if specify an older version.
Ref: https://travis-ci.org/rails/rails/jobs/295553738#L1718
Follow up of #31023
|
|
|
|
|
| |
It's causing bug report template tests to fail. https://travis-ci.org/rails/rails/jobs/295520851
This seems an issue of bundler. Ref: https://github.com/bundler/bundler/issues/6072
|
| |
|
| |
|
|
|
|
|
| |
Most interesting to us, 2.4.2 and 2.3.5 include the fix for
https://bugs.ruby-lang.org/issues/13632
|
|
|
|
| |
http://jruby.org/2017/09/06/jruby-9-1-13-0.html
|
| |
|
|
|
|
|
| |
Travis CI new default Ubuntu Trusty supports 9.6
https://docs.travis-ci.com/user/database-setup/#Using-a-different-PostgreSQL-Version
|
|
|
|
|
| |
- Travis CI is migrating Ubuntu version to Trusty
- MariaDB 10.2 is supported on Ubuntu Trusty
|
|
|
|
| |
The value isn't actually secret, so I've kept it as a comment.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Adds RedisAdapterTest::AlternateConfiguration to account
for a relatively common alternative setup, as it’s used
as the first example in the
[Redis rubygem](https://github.com/redis/redis-rb#getting-started)
- Supplies original RedisAdapterTest with more complete
redis:// url format by adding a ‘userinfo’ (blank user),
so that it resembles the alternate configuration
- Supplies original EventedRedisAdapterTest with more complete
redis:// url as well
- Adds before_script to start redis-server with password as a daemon
and with explicit defaults copied from the default redis.conf
(Instead of using Travis' default init/upstart scripts for `redis` service)
|
|
|
|
| |
http://jruby.org/2017/06/15/jruby-9-1-12-0.html
|
|
|
|
| |
http://jruby.org/2017/05/25/jruby-9-1-10-0.html
|
|
|
|
|
|
|
| |
This version lock added by 3d890b66c1bfbdcabb7ef66e0774e0f01e2ed5d6.
But original issue is fixed with bundler 1.15.
Ref: https://github.com/rubygems/rubygems/issues/1911#issuecomment-300148516
|
|
|
|
| |
http://jruby.org/2017/05/16/jruby-9-1-9-0
|
|
|
|
|
| |
It's causing a test to fail, and we're not yet sure what (if anything)
we should be doing differently. See rubygems/rubygems#1911.
|
|
|
|
|
|
|
|
|
| |
mtsmfm/disable-referential-integrity-without-superuser-privilege-take-2"
This reverts commit c1faca6333abe4b938b98fedc8d1f47b88209ecf, reversing
changes made to 8c658a0ecc7f2b5fc015d424baf9edf6f3eb2b0b.
See https://github.com/rails/rails/pull/27636#issuecomment-297534129
|
|
|
|
|
|
| |
Also, explicitly apply the order: generate_subscripts is unlikely to
start returning values out of order, but we should still be clear about
what we want.
|
|
|
|
| |
Related #28532, #27636
|
|
|
|
| |
https://www.ruby-lang.org/en/news/2017/03/30/ruby-2-3-4-released/
|
|
|
|
| |
https://www.ruby-lang.org/en/news/2017/03/28/ruby-2-2-7-released/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
privileges (take 2)
Re-create https://github.com/rails/rails/pull/21233
eeac6151a5 was reverted (127509c071b4) because it breaks tests.
----------------
ref: 72c1557254
- We must use `authors` fixture with `author_addresses` because of its foreign key constraint.
- Tests require PostgreSQL >= 9.4.2 because it had a bug about `ALTER CONSTRAINTS` and fixed in 9.4.2.
|
|
|
|
| |
https://www.ruby-lang.org/en/news/2017/03/22/ruby-2-4-1-released/
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
And let's see if it still fails...
|
|
|
|
|
|
|
|
|
|
| |
mtsmfm/disable-referential-integrity-without-superuser-privileges"
This reverts commit eeac6151a55cb7d5f799e1ae33aa64a839cbc3aa, reversing
changes made to 5c40239d3104543e70508360d27584a3e4dc5baf.
Reason: Broke the isolated tests.
https://travis-ci.org/rails/rails/builds/188721346
|
|\
| |
| |
| |
| | |
mtsmfm/disable-referential-integrity-without-superuser-privileges
Use `SET CONSTRAINTS` for `disable_referential_integrity` without superuser privileges
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
privileges
ref: 72c1557254
- We must use `authors` fixture with `author_addresses` because of its foreign key constraint.
- Tests require PostgreSQL >= 9.4.2 because it had a bug about `ALTER CONSTRAINTS` and fixed in 9.4.2.
|
| | |
|