rk35xx/rockchip-rk3588: vendor u-boot: more logs for 0-byte-dtb (or not)

- so we can take a single look at CI logs and see what breaks or not and where

Author: rpardini

config/sources/families/rk35xx.conf

@@ -65,7 +65,9 @@ function check_uboot_produced_binary_file__check_vendor_uboot_for_0_byte_dtb() {
 
 	# Run dumpimage -l, grep it for string 'Data Size:    0 Bytes', if found, exit_with_error
 	if dumpimage -l "${binfile}" | grep -q "Data Size:    0 Bytes"; then
-		exit_with_error "u-boot for ${BOARD}::${BRANCH}::${base_binfile}: Error: The produced u-boot.itb file contains a 0-byte DTB; built on ${HOSTRELEASE}"
+		exit_with_error "u-boot for ${BOARD}::${BRANCH}::${base_binfile}: Error: The produced u-boot.itb file contains a 0-byte DTB; built on ${HOSTRELEASE} (${RUNNER_NAME}::${RUNNER_ENVIRONMENT}::${RUNNER_ARCH})"
+	else
+		display_alert "u-boot for ${BOARD}::${BRANCH}::${base_binfile}" "OK, produced u-boot.itb does NOT have 0-byte-dtb; built on ${HOSTRELEASE} (${RUNNER_NAME}::${RUNNER_ENVIRONMENT}::${RUNNER_ARCH})" "notice" # logs to CI log
 	fi
 
 	return 0

config/sources/families/rockchip-rk3588.conf

@@ -63,7 +63,9 @@ function check_uboot_produced_binary_file__check_vendor_uboot_for_0_byte_dtb() {
 
 	# Run dumpimage -l, grep it for string 'Data Size:    0 Bytes', if found, exit_with_error
 	if dumpimage -l "${binfile}" | grep -q "Data Size:    0 Bytes"; then
-		exit_with_error "u-boot for ${BOARD}::${BRANCH}::${base_binfile}: Error: The produced u-boot.itb file contains a 0-byte DTB; built on ${HOSTRELEASE}"
+		exit_with_error "u-boot for ${BOARD}::${BRANCH}::${base_binfile}: Error: The produced u-boot.itb file contains a 0-byte DTB; built on ${HOSTRELEASE} (${RUNNER_NAME}::${RUNNER_ENVIRONMENT}::${RUNNER_ARCH})"
+	else
+		display_alert "u-boot for ${BOARD}::${BRANCH}::${base_binfile}" "OK, produced u-boot.itb does NOT have 0-byte-dtb; built on ${HOSTRELEASE} (${RUNNER_NAME}::${RUNNER_ENVIRONMENT}::${RUNNER_ARCH})" "notice" # logs to CI log
 	fi
 
 	return 0