travis: run Coverity after Fuzzit-Fuzzing

Coverity is unpredictable and, according to a notification I received
yeserday, it will be upgraded on June 17. During the upgrade
it might be offline for 3 days, af far as I understand. Anyway, Travis
stops as soon as a stage fails so it makes sense to put stages that
are likely to fail at the end so that the others have a chance to
do what they are supposed to do.

https://community.synopsys.com/s/topic/0TO2H0000001CN7WAM/coverity-scan-status

diff --git a/.travis.yml b/.travis.yml
index 864d84f1707076c191de132cb2bfcbe0b8385290..f41b43ed22844859df06efcf25fd1beeaed49869 100644 (file)
--- a/.travis.yml
+++ b/.travis.yml
@@ -11,11 +11,11 @@ env:
         - REPO_ROOT="$TRAVIS_BUILD_DIR"
 
 stages:
-    # Run Coverity periodically instead of for each commit/PR
-    - name: Coverity
+    - name: Fuzzit-Fuzzing
       if: type = cron
 
-    - name: Fuzzit-Fuzzing
+    # Run Coverity periodically instead of for each commit/PR
+    - name: Coverity
       if: type = cron
 
 jobs: