From ccf54ad6eba3ed7d42fd4e0310283e7b0d15124a Mon Sep 17 00:00:00 2001
From: Isaac van Bakel <ivb@vanbakel.io>
Date: Wed, 24 Oct 2018 17:34:00 +0100
Subject: [PATCH] Try to change travis build ordering to fix compiletests
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.
---
.travis.yml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index 588975f..6305646 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -6,10 +6,12 @@ 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
+ - cargo test --all --exclude maud_macros
- (cd benchmarks && cargo bench --no-run)
- |
CLIPPY_STATUS=0