tor

commit 6ed3d8dbd180aa72e2c9b3fa4835fb82e0f60556
parent 967460389a2f5dd70f75dd753a0d9ff97292e5b2
Author: Nick Mathewson <nickm@torproject.org>
Date:   Mon, 23 Sep 2019 15:04:54 -0400

Try using make -k in Travis configuration

Frequently, when a patch fails, it has failures in several files.
Using the "-k" flag will let us learn all the compilation errors,
not just the first one that the compiler hits.

Based on a patch by rl1987.

Diffstat:
M
.travis.yml
 | 
6
++++--
A
changes/ticket31372_travis
 | 
4
++++

2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/.travis.yml b/.travis.yml
@@ -15,8 +15,10 @@ os:
 ## OS and compiler.
 env:
   global:
-    ## The Travis CI environment allows us two cores, so let's use both.
-    - MAKEFLAGS="-j 2"
+    ## The Travis CI environment allows us two cores, so let's use both.  Also,
+    ## let's use the "-k" flag so that we get all of the compilation failures,
+    ## not just the first one.
+    - MAKEFLAGS="-k -j 2"
     ## We turn on hardening by default
     ## Also known as --enable-fragile-hardening in 0.3.0.3-alpha and later
     - HARDENING_OPTIONS="--enable-expensive-hardening"
diff --git a/changes/ticket31372_travis b/changes/ticket31372_travis
@@ -0,0 +1,4 @@
+  o Minor features (continuous integration):
+    - When building on Travis, pass the "-k" flag to make, so that
+      we are informed of all compilation failures, not just the first
+      one or two. Closes part of ticket 31372.