free_mutant/.travis.yml

language: ruby
script: 'bundle exec rake spec'
rvm:
  - 1.8.7
  - 1.9.2
  - 1.9.3
  - 2.0.0
  - ruby-head
  - rbx-19mode
matrix:
  allow_failures:
    # No mutators for 1.8 specifc AST nodes
    - rvm: rbx-18mode
    - rvm: 1.8.7
    # We'll see what happens
    - rvm: ruby-head
    - rvm: 2.0.0
notifications:
  email:
    - mbj@seonic.net
Finalize method matching * Add tests for all edge cases I could create * Add infrastructure for loading mutations into the vm. * The fun part is next! 2012-07-26 13:25:23 -04:00			`language: ruby`
Use spec target on travis ci until issues with flay are solved * Flay gives differend score on CI than on local system. Most likely an rbx version differenceis are the source of this behavior. 2012-08-19 22:57:14 -04:00			`script: 'bundle exec rake spec'`
Finalize method matching * Add tests for all edge cases I could create * Add infrastructure for loading mutations into the vm. * The fun part is next! 2012-07-26 13:25:23 -04:00			`rvm:`
Allow failures on 1.8 and rbx 2012-12-07 05:57:57 -05:00			`- 1.8.7`
Make mutant run under MRI 1.9. * Add a Mutant::Loader::Eval that loads code via Kernel#eval * Move Mutnat::Loader to Mutant::Loader::Rubinius (currently not used) 2012-11-21 14:31:01 -05:00			`- 1.9.2`
			`- 1.9.3`
Test against 2.0.0 on travis 2013-03-01 11:08:16 -05:00			`- 2.0.0`
Add ruby-head to travis 2013-01-02 07:04:20 -05:00			`- ruby-head`
Reenable travis for rbx 2012-12-06 17:25:12 -05:00			`- rbx-19mode`
Allow failures on 1.8 and rbx 2012-12-07 05:57:57 -05:00			`matrix:`
			`allow_failures:`
Adjust allowed failures on travis 2012-12-12 14:20:57 -05:00			`# No mutators for 1.8 specifc AST nodes`
Fix whitespace 2013-04-17 23:31:21 -04:00			`- rvm: rbx-18mode`
Allow failures on 1.8 and rbx 2012-12-07 05:57:57 -05:00			`- rvm: 1.8.7`
Add ruby-head to travis 2013-01-02 07:04:20 -05:00			`# We'll see what happens`
			`- rvm: ruby-head`
Test against 2.0.0 on travis 2013-03-01 11:08:16 -05:00			`- rvm: 2.0.0`
Finalize method matching * Add tests for all edge cases I could create * Add infrastructure for loading mutations into the vm. * The fun part is next! 2012-07-26 13:25:23 -04:00			`notifications:`
			`email:`
			`- mbj@seonic.net`