aboutsummaryrefslogtreecommitdiffstats
path: root/RAILS_VERSION
diff options
context:
space:
mode:
authoryuuji.yaginuma <yuuji.yaginuma@gmail.com>2018-09-13 14:07:26 +0900
committerYuji Yaginuma <yuuji.yaginuma@gmail.com>2018-09-14 07:16:19 +0900
commit82556cd452563abcf985ca33d1c82dfa3d4fc443 (patch)
tree13e1bb370546d26b8067db791ad80fccf614fb18 /RAILS_VERSION
parentc49139dd99642a4c2130fac7b2751ae7f22300b2 (diff)
downloadrails-82556cd452563abcf985ca33d1c82dfa3d4fc443.tar.gz
rails-82556cd452563abcf985ca33d1c82dfa3d4fc443.tar.bz2
rails-82556cd452563abcf985ca33d1c82dfa3d4fc443.zip
Enable `sudo` only in the required build
Currently, PostgreSQL + Ruby 2.5.1 build has failed. https://travis-ci.org/rails/rails/jobs/427502723#L2940-L2942 https://travis-ci.org/rails/rails/jobs/427496382#L2921-L2923 https://travis-ci.org/rails/rails/jobs/427470858#L2921-L2923 This is because PostgreSQL server abnormally terminates when ramfs becomes full. Ref: https://travis-ci.org/rails/rails/jobs/427960998#L7614 This occurs since d54d0c95750e2693da495b75ac5fa0280253972d. In d54d0c95750e2693da495b75ac5fa0280253972d, `sudo` is used in preprocessing for setting MySQL. In Travis, even if specified `sudo: false`, when using `sudo` in build, sudo-enabled infrastructure is used. https://docs.travis-ci.com/user/reference/overview/#virtualisation-environment-vs-operating-system As container-based infrastructure was changed to sudo-enabled infrastructure, the disk settings etc were also changed, it seems that this phenomenon occurred. This can also be handled by extending ramfs(https://github.com/travis-ci/travis-ci/issues/9036#issuecomment-357189213). However, using sudo-enabled in all builds affects the execution time of build, so I think that it is good to use sudo-enabled only in the necessary builds.
Diffstat (limited to 'RAILS_VERSION')
0 files changed, 0 insertions, 0 deletions