[SERVER-66309] getLogs command truncated output causes jstest to fail Created: 09/May/22 Updated: 29/Oct/23 Resolved: 16/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Witten (Inactive) | Assignee: | Hana Pearlman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 29 | ||||
| Description |
|
JS test jstests/sharding/query/lookup_unionWith_subpipeline_local_read.js requires being able to read enough server logs in order to pass (using the getLog command). It isn't reading enough of them. |
| Comments |
| Comment by Githook User [ 16/May/22 ] |
|
Author: {'name': 'Hana Pearlman', 'email': 'hana.pearlman@mongodb.com', 'username': 'HanaPearlman'}Message: |
| Comment by Hana Pearlman [ 12/May/22 ] |
|
We can see in the logs on evergreen that the local read being expected in the test is in fact happening. So, this is a test-only issue. I thought this test was safe after some changes we made in October ( |