Skip to content

Commit 1775eb2

Browse files
committed
scripts/check-logs.py: Print error from TuxSuite better
Currently, we assume if we do not get a "complete" status back from the build, the build is not completed. Recently however, there have been an increase in internal TuxSuite infrastructure errors, which are not obvious upon inspection. If the build status is "error", print out the status message and exit early, as we know that the build is done since it never started :) Signed-off-by: Nathan Chancellor <[email protected]>
1 parent d5a82a1 commit 1775eb2

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

scripts/check-logs.py

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,12 @@ def verify_build():
5858
retries = 0
5959
max_retries = 9
6060
while retries < max_retries:
61-
if build["tuxbuild_status"] == "complete":
61+
# build never started
62+
if (build_status := build['tuxbuild_status']) == 'error':
63+
print_red(f"msg from tuxsuite: {build['status_message']}")
64+
sys.exit(1)
65+
# build is finished
66+
elif build_status == "complete":
6267
break
6368

6469
if retries:

0 commit comments

Comments
 (0)