mirror of
https://github.com/rubyjs/therubyracer
synced 2023-03-27 23:21:42 -04:00
d969b1cdb9
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.
36 lines
594 B
YAML
36 lines
594 B
YAML
#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
|
|
- bundle exec rspec spec/v8/context_spec.rb
|
|
- bundle exec rspec spec/mem
|
|
sudo: false
|
|
addons:
|
|
apt:
|
|
sources:
|
|
- ubuntu-toolchain-r-test
|
|
packages:
|
|
- gcc-4.8
|
|
- g++-4.8
|
|
- clang
|