[SERVER-35800] resmoke.py should retry getting a build_id and test_id from logkeeper Created: 26/Jun/18 Updated: 29/Oct/23 Resolved: 09/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.9, 4.0.3, 4.1.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Robert Guo (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | tig-qwin-eligible, tig-resmoke | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v4.0, v3.6
|
||||||||||||
| Sprint: | TIG 2018-07-30, TIG 2018-08-13 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 16 | ||||||||||||
| Story Points: | 2 | ||||||||||||
| Description |
|
The changes from Note: Retrying the request to get a build_id or new test_id is safe as it simply inserts a new document. The only quirk is that the "Job logs" tab may show extra entries in the case that resmoke.py never received a response from the logkeeper application server but the database still eventually did the work. |
| Comments |
| Comment by Githook User [ 20/Sep/18 ] |
|
Author: {'name': 'Robert Guo', 'email': 'robert.guo@10gen.com', 'username': 'guoyr'}Message: (cherry picked from commit cc00af6b6f43c2df8e649ae19040ab7df19db950) |
| Comment by Githook User [ 20/Sep/18 ] |
|
Author: {'name': 'Robert Guo', 'email': 'robert.guo@10gen.com', 'username': 'guoyr'}Message: |
| Comment by Githook User [ 09/Aug/18 ] |
|
Author: {'name': 'Robert Guo', 'email': 'robert.guo@10gen.com', 'username': 'guoyr'}Message: |