[SERVER-48647] Unit tests fail trying to parse TSAN output Created: 08/Jun/20 Updated: 14/Jul/20 Resolved: 17/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 4.5 Desired |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ryan Egesdahl (Inactive) | Assignee: | Ryan Egesdahl (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Sprint: | Dev Platform 2020-06-29 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||
| Description |
|
As we are standing up TSAN, we have discovered that the unit tests are failing because TSAN output is not the JSON the test harness is expecting to parse. What we actually want to have happen is that the test fails and we can see the entire TSAN report so the cause of the failure is obvious from the logs. |
| Comments |
| Comment by Ryan Egesdahl (Inactive) [ 17/Jun/20 ] |
|
Another team took on the work while we weren't looking and fixed it for us. |