Run specs on Ruby 2.7 too to make sure they keep passing

* With keyword argument changes, it's more likely to break only 2.7 and
  not other versions.
* A few specs were broken on 2.7.0 recently, this should catch them earlier.
This commit is contained in:
Benoit Daloze 2020-01-28 18:37:42 +01:00
Родитель 766f8a7a60
Коммит 6321a68582
1 изменённых файлов: 15 добавлений и 2 удалений

Просмотреть файл

@ -362,7 +362,7 @@ env:
-Wunused-variable' -Wunused-variable'
- LDFLAGS=-Wno-unused-command-line-argument - LDFLAGS=-Wno-unused-command-line-argument
- &rubyspec - &rubyspec24
name: Check ruby/spec version guards on Ruby 2.4 name: Check ruby/spec version guards on Ruby 2.4
language: ruby language: ruby
rvm: 2.4.9 rvm: 2.4.9
@ -374,6 +374,18 @@ env:
after_failure: after_failure:
- echo "ruby/spec failed on Ruby 2.4. This is likely because of a missing ruby_version_is guard, please add it. See spec/README.md." - echo "ruby/spec failed on Ruby 2.4. This is likely because of a missing ruby_version_is guard, please add it. See spec/README.md."
- &rubyspec27
name: Check ruby/spec version guards on Ruby 2.7
language: ruby
rvm: 2.7.0
before_install:
install:
before_script: chmod -R u+w spec/ruby
# -j randomly hangs.
script: ruby -C spec/ruby ../mspec/bin/mspec .
after_failure:
- echo "ruby/spec failed on Ruby 2.7. This is likely because of a missing ruby_version_is guard, please add it. See spec/README.md."
- &baseruby - &baseruby
name: "BASERUBY: Ruby 2.2" name: "BASERUBY: Ruby 2.2"
<<: *gcc-8 <<: *gcc-8
@ -425,7 +437,8 @@ matrix:
- <<: *pedanticism - <<: *pedanticism
- <<: *assertions - <<: *assertions
- <<: *baseruby - <<: *baseruby
- <<: *rubyspec - <<: *rubyspec24
- <<: *rubyspec27
- <<: *dependency - <<: *dependency
# Build every commit (Allowed Failures): # Build every commit (Allowed Failures):
- <<: *ASAN - <<: *ASAN