[SERVER-62935] Add timestamp with Failed to Load message in jstests Created: 24/Jan/22 Updated: 29/Oct/23 Resolved: 18/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Shreyas Kalyan | Assignee: | Gabriel Marks |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | dp-qp-stakeholder-request-2022-01, former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Security 2022-04-18, Security 2022-05-02 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Sometimes when diagnosing a failure in a BF, it is hard to determine when exactly the failure happened - there may be missing log statements etc. In these situations, it would be helpful to have timestamps associated with the Javascript backtrace that gets outputted from the tests. For example, in BF-24122 it's hard to tell when the assert.soon failed. Because it causes the process to terminate, we can make some assumptions from the log line below failed to load, but it would be nice to have a timestamp on the actual failure message. |
| Comments |
| Comment by Githook User [ 18/Apr/22 ] |
|
Author: {'name': 'Gabriel Marks', 'email': 'gabriel.marks@mongodb.com', 'username': 'marksg07'}Message: |