[glib-networking/mcatanzaro/ci: 2/2] ci: run the tests fewer times




commit 9f373e602ed6d9468f3a2e90701b06a92e3b2366
Author: Michael Catanzaro <mcatanzaro redhat com>
Date:   Tue Jun 28 12:30:33 2022 -0500

    ci: run the tests fewer times
    
    We're currently exceeding the max log output length, which is not
    useful. Running the tests less often makes it harder to detect race
    conditions, but detecting problems does not good if we have no logs to
    see what they are, so the status quo 1000 runs is not useful.
    
    I first tried 100 runs, but we were still hitting the output length
    limit when we were approximately 20% through. So let's try just 10 runs.
    I fear this is too little to find unlikely race conditions, but it's
    better than reducing debug verbosity.
    
    Besides, the tests have been flaky for several years, and I haven't
    managed to fix them yet. The benefit of detecting flakiness is
    reduced if I don't do anything about it.
    
    This will also make our CI way faster.

 .gitlab-ci.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
---
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 86cc0e66..a2fc6d4a 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -17,7 +17,7 @@ fedora-x86_64:
             -Dwerror=true
             _build/
     - meson compile -C _build/
-    - meson test -v -C _build/ --repeat=1000
+    - meson test -v -C _build/ --repeat=500
     - meson install -C _build/
     - ninja -C _build coverage-html
   artifacts:


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]