mlua/.travis.yml

language: rust
env:
  - RUSTFLAGS="-D warnings"
before_script:
  rustup component add rustfmt-preview
matrix:
  include:
    - rust: stable
      script:
        - cargo fmt --all -- --check
        - cargo test --all --verbose
    - rust: beta
      script: cargo test --all --verbose
    - rust: nightly 
      script: cargo test --all --verbose --features compiletest_rs
  allow_failures:
    - rust: nightly
Add travis-ci script 2017-05-22 23:00:32 -04:00			`language: rust`
Deny warnings on Travis Always treating warnings as errors makes development annoying ("ugh I don't want to fix this right now"), but ignoring them quickly leaves them unfixed and shines a bad light on the project when other people want build it ("hmm, this crate's a little to... yellow for my taste"). I've found that this is pretty much a perfect middle ground (even though rlua doesn't require CI to pass before merging PRs). 2017-08-02 17:13:02 -04:00			`env:`
			`- RUSTFLAGS="-D warnings"`
add rustfmt checks to travis (stable channel) 2018-10-13 17:48:16 -04:00			`before_script:`
			`rustup component add rustfmt-preview`
Attempt to enable compiletest_rs on nightly on travis 2018-02-10 00:26:48 -05:00			`matrix:`
			`include:`
			`- rust: stable`
add rustfmt checks to travis (stable channel) 2018-10-13 17:48:16 -04:00			`script:`
fix broken .travis.yml 2018-10-13 17:51:44 -04:00			`- cargo fmt --all -- --check`
			`- cargo test --all --verbose`
Attempt to enable compiletest_rs on nightly on travis 2018-02-10 00:26:48 -05:00			`- rust: beta`
fix broken .travis.yml 2018-10-13 17:51:44 -04:00			`script: cargo test --all --verbose`
Attempt to enable compiletest_rs on nightly on travis 2018-02-10 00:26:48 -05:00			`- rust: nightly`
better cargo test flags for travis 2018-09-02 02:53:30 -04:00			`script: cargo test --all --verbose --features compiletest_rs`
Add travis-ci script 2017-05-22 23:00:32 -04:00			`allow_failures:`
			`- rust: nightly`