[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: |
|
||||
| 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".
|