ccf54ad6eb
Multiple versions of the maud base crate get built, so compiletest doesn't know which one to use in the same way that cargo would. A possible solution is to build a canonical version of the crate first (no features) and then explicitly run the compiletest tests. After, we run builds and tests as normal, excluding the compiletest tests.
21 lines
626 B
YAML
21 lines
626 B
YAML
language: rust
|
|
rust: nightly
|
|
sudo: false
|
|
|
|
before_script:
|
|
- rustup component add clippy-preview --toolchain=nightly
|
|
|
|
script:
|
|
- (cd maud && cargo build)
|
|
- (cd maud_macros && cargo test)
|
|
- (cd maud && cargo build --features="iron")
|
|
- (cd maud && cargo build --features="rocket")
|
|
- (cd maud && cargo build --features="actix-web")
|
|
- cargo test --all --exclude maud_macros
|
|
- (cd benchmarks && cargo bench --no-run)
|
|
- |
|
|
CLIPPY_STATUS=0
|
|
for package in maud_htmlescape maud_macros maud maud_extras; do
|
|
(cd $package && cargo clippy -- -D warnings) || CLIPPY_STATUS=$?
|
|
done
|
|
(exit $CLIPPY_STATUS)
|