fix: add retry logic to CI VM status and log upload functions #1012
+146
−17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



Summary
postStatusandsendLogFilefunctions now check curl exit codes and HTTP response codessendLogFilefunction in Windows script (previously inline)Root Cause
Test 7935 completed all 237 tests but never reported completion to the server. The test remained stuck in "testing" state with 100% progress. Investigation revealed that the CI VM scripts had no error handling for status POST requests - if the curl request failed due to network issues or server timeout, the script would continue without retrying and then shut down, leaving the test stuck forever.
Changes
Linux (
install/ci-vm/ci-linux/ci/runCI):postStatus(): Now retries up to 3 times with exponential backoffsendLogFile(): Now retries up to 3 times with exponential backoffWindows (
install/ci-vm/ci-windows/ci/runCI.bat)::postStatus: Now retries up to 3 times with exponential backoff:sendLogFile: New function with retry logic (previously inline curl call):haltAndCatchFire: Now usessendLogFilefunctionTest plan
🤖 Generated with Claude Code