therubyracer/.travis.yml

#cache: bundler
rvm:
  - 2.1.0
  - 2.0.0
  - 1.9.3
  - 1.9.2
  - 1.8.7
  - rbx-2.2.3
matrix:
  allow_failures:
    - rvm: 1.9.3
    - rvm: 1.9.2
    - rvm: 1.8.7
    - rvm: rbx-2.2.3
env:
  - CXX=g++-4.8
  - CXX=clang++
notifications:
  recipients:
    - cowboyd@thefrontside.net
before_install:
  - gem update --system 2.1.11
script:
  - bundle exec rake compile
  - bundle exec rspec spec/c spec/v8/context_spec.rb spec/v8/isolate_spec.rb
  - bundle exec rspec spec/mem
sudo: false
addons:
  apt:
    sources:
    - ubuntu-toolchain-r-test
    packages:
    - gcc-4.8
    - g++-4.8
    - clang
disable bundler cache that contains yanked gems 2015-07-12 14:26:37 -05:00			`#cache: bundler`
add Travis CI config 2012-02-17 09:12:14 -06:00			`rvm:`
Add Ruby 2.1.0 to .travis.yml 2013-12-29 10:56:42 +01:00			`- 2.1.0`
add ruby 2.0 to travis file 2013-03-28 09:33:15 -05:00			`- 2.0.0`
add Travis CI config 2012-02-17 09:12:14 -06:00			`- 1.9.3`
Add Ruby 2.1.0 to .travis.yml 2013-12-29 10:56:42 +01:00			`- 1.9.2`
add Travis CI config 2012-02-17 09:12:14 -06:00			`- 1.8.7`
bump rbx build to use v2.2.3 2014-01-02 23:49:39 +02:00			`- rbx-2.2.3`
allow failures on older versions of ruby. We can decide whether to backport later 2015-07-11 21:13:09 -05:00			`matrix:`
			`allow_failures:`
			`- rvm: 1.9.3`
			`- rvm: 1.9.2`
			`- rvm: 1.8.7`
rbx: not to big to fail. 2015-07-13 13:57:10 -05:00			`- rvm: rbx-2.2.3`
allow using a custom compiler 2015-07-12 14:05:26 -05:00			`env:`
			`- CXX=g++-4.8`
			`- CXX=clang++`
add Travis CI config 2012-02-17 09:12:14 -06:00			`notifications:`
			`recipients:`
			`- cowboyd@thefrontside.net`
workaround rubygems#763 to fix build on ruby 1.8.7 2014-01-02 23:33:08 +02:00			`before_install:`
			`- gem update --system 2.1.11`
only run C spec compiled with Clang In order to make sure we have valid failures on this branch, and not just a bunch of false negatives, we're only running the C specs, and building with clang. Eventually, we'll merge in support for gcc and more of the test suite. For now, we want to only include the specs we things should be passing 2015-07-11 21:08:38 -05:00			`script:`
Don't hardcode g++ into build 2015-07-12 14:12:50 -05:00			`- bundle exec rake compile`
add pre-emption APIS v8 4.5 has very convenient APIs for interrupting potentially long running JavaScript code. This exposes those APIs to Ruby code so that it can place its own limits on the CPU resources consumed by V8. 2015-08-14 16:04:27 +03:00			`- bundle exec rspec spec/c spec/v8/context_spec.rb spec/v8/isolate_spec.rb`
add back the basics of memory testing. This adds back the memory tests which ensure The Ruby Racer's stability. It also includes the changes needed to make these initial specs pass. At this point to disallow calling Dispose() directly on the underlying Isolate. If you do, then you could have all of the Ruby objects happily sitting in memory, but trying to use them would result in a segfault for trying to use a dead isolate. In order to avoid that, we'd have to put in safeguards everywhere to make sure for any operation on any context or object, that it's isolate was still alive. In order to reduce the complexity of memory management, the safest thing is to let the garbage collection hook dispose of the isolate itself. That way there is no doubt that the isolate is no longer in use. 2015-07-28 17:57:01 +03:00			`- bundle exec rspec spec/mem`
install modern g++ and clang befondhand 2015-07-11 22:28:29 -05:00			`sudo: false`
			`addons:`
			`apt:`
			`sources:`
			`- ubuntu-toolchain-r-test`
			`packages:`
			`- gcc-4.8`
			`- g++-4.8`
			`- clang`