From 401079660b2326fe5ecb7f0ee2456e02730a4218 Mon Sep 17 00:00:00 2001 From: Said Boudjelda Date: Fri, 30 Oct 2026 11:26:10 +0100 Subject: [PATCH] fix(ci): Grafana compat check ignores cancelled queries The Dashboards job failed on main (run 41032511187) although all four Grafanas rendered 12/12 boards with 0 panel errors. Grafana 11.6.6 logged "Failed getting data source" err="context canceled": a query the browser dropped when it moved on to the next board. The log scan counted it as a failure. A data source that really fails still shows as a panel error. --- scripts/check-grafana-compat.sh | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/scripts/check-grafana-compat.sh b/scripts/check-grafana-compat.sh index eb77001e..360bab03 100755 --- a/scripts/check-grafana-compat.sh +++ b/scripts/check-grafana-compat.sh @@ -148,8 +148,10 @@ for version in "${VERSIONS[@]}"; do # "Failed to lock and execute the migration of API keys to service accounts" # error="database is locked". A lock bad enough to break provisioning would # already show up in compat.py as a missing board, so nothing is hidden. + # err="context canceled" is a query the browser dropped when it moved on to + # the next board; a data source that really failed shows as a panel error. errors=$(docker logs kates-compat-grafana 2>&1 \ - | grep -iE 'level=error' | grep -viE 'grafana\.com|x509|plugin|update|database is locked' | head -3 || true) + | grep -iE 'level=error' | grep -viE 'grafana\.com|x509|plugin|update|database is locked|context canceled' | head -3 || true) [ -n "$errors" ] && { echo " Grafana logged:"; echo "$errors" | sed 's/^/ /'; rc=1; } done