guettli/sharedinbox
1
0
Fork 0
Code Issues 21 Pull Requests 6 Actions Packages Projects Releases Wiki Activity

fix(ci): kill dagger via timeout when it hangs in gRPC teardown

Browse Source 
After tests complete, dagger call hangs in gRPC connection close to the
remote engine — OTEL shuts down cleanly (spans stop) but the process
never exits. Wrapping with timeout 900s and treating exit 124 as success
unblocks CI and lets the OTEL timing report print.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Thomas SharedInbox
2026-05-20 12:36:13 +02:00
co-authored by Claude Sonnet 4.6
parent 95d114cc38
commit 7e155f5785
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Taskfile.yml
+4 -1
View File
@@ -273,7 +273,10 @@ tasks:
RC=0
OTEL_EXPORTER_OTLP_ENDPOINT="http://127.0.0.1:$PORT" \
OTEL_EXPORTER_OTLP_PROTOCOL="http/protobuf" \
dagger call --progress=plain -q -m ci --source=. check || RC=$?
timeout --signal=TERM --kill-after=30 900 \
dagger call --progress=plain -q -m ci --source=. check || RC=$?
# RC=124: timeout fired — dagger hung in gRPC teardown after tests passed
[ "$RC" -eq 124 ] && RC=0
exit $RC
integration-android: