ci/bare-metal: Log why our run restarts when it does.
authorEric Anholt <eric@anholt.net>
Mon, 31 Aug 2020 20:41:57 +0000 (13:41 -0700)
committerEric Anholt <eric@anholt.net>
Thu, 3 Sep 2020 23:22:43 +0000 (23:22 +0000)
It would be confusing to see a job quietly restart itself in the middle.

Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6529>

.gitlab-ci/bare-metal/cros_servo_run.py

index 9d7cfa488cd1eb91a47c84da9c360a40fc32f14e..b53763be2590974f9c3f21e9db2627cea41b864f 100755 (executable)
@@ -96,6 +96,7 @@ class CrosServoRun:
             # the system sometimes, possibly dependent on ambient temperature
             # in the farm.
             if re.search("POWER_GOOD not seen in time", line):
+                print("Detected intermittent poweron failure, restarting run...")
                 return 2
 
             # The Cheza firmware seems to occasionally get stuck looping in
@@ -105,6 +106,7 @@ class CrosServoRun:
             if re.search("R8152: Bulk read error 0xffffffbf", line):
                 tftp_failures += 1
                 if tftp_failures >= 100:
+                    print("Detected intermittent tftp failure, restarting run...")
                     return 2
 
             result = re.search("bare-metal result: (\S*)", line)