From b447032489af1d1578d36d9084d93706e46a9eac Mon Sep 17 00:00:00 2001
From: Tom Krizek <tkrizek@isc.org>
Date: Mon, 13 Mar 2023 13:36:24 +0100
Subject: [PATCH] Find errors in dig output in system tests

Facilitate faster system test failure identification and debugging by
checking any dig outputs for errors, which are typically indicative of
CI runner network / load issues.

(cherry picked from commit 940e160c06e95c10ac58c3495dbd63daef1797b9)
---
 .gitlab-ci.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index ad1d7f0b11..7d2f7ba0c7 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -323,6 +323,7 @@ stages:
     - REALSOURCEDIR="$PWD"
     - test -n "${OUT_OF_TREE_WORKSPACE}" && cd "${OUT_OF_TREE_WORKSPACE}"
     - cat bin/tests/system/test-suite.log
+    - find bin/tests/system -name "*dig.*" | xargs grep "error"
     - *find_python
     - >
       "$PYTHON" "$REALSOURCEDIR"/bin/tests/convert-trs-to-junit.py . > "$CI_PROJECT_DIR"/junit.xml
@@ -345,6 +346,7 @@ stages:
   <<: *system_test_common
   after_script:
     - cat bin/tests/system/test-suite.log
+    - find bin/tests/system -name "*dig.*" | xargs grep "error"
     - *find_python
     - *parse_tsan
     - >