[SERVER-40921] Failure to download debug symbols should be marked as a "System Failure" instead of a timeout Created: 30/Apr/19  Updated: 27/Oct/23  Resolved: 30/Apr/19

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Justin Seyster Assignee: Max Hirschhorn
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Linked BF Score: 7

 Description   

If I'm reading BF-13062 correctly, it failed because it wasn't able to download the debug symbols .tgz file and ended up marked as a timed out test.

I think that either the "fetch debugsymbols" command should have failed with "System Failure" when all 10 download attempts failed or the "extract debugsymbols" command should have failed with "System Failure" when it didn't see any file to extract.



 Comments   
Comment by Max Hirschhorn [ 30/Apr/19 ]

justin.seyster, the task timed out after 15 minutes of tests not completing. We then failed to download the debug symbols from S3 for a reason that's opaque to me. I'm going to close this as "Works as designed".

[2019/04/29 16:49:22.555] [executor:js_test:job5] 2019-04-29T16:49:22.555+0000 reconfig_during_election.js ran in 32.02 seconds.
[2019/04/29 17:04:23.074] Command stopped early: context canceled
[2019/04/29 17:04:23.074] Running task-timeout commands.
[2019/04/29 17:04:23.624] Running command 's3.get' in "fetch debugsymbols archive" (step 1 of 5)
...
[2019/04/29 17:14:41.556] Command failed: S3 get failed after 10 attempts

Generated at Thu Feb 08 04:56:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.