[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:
Depends
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: SERVER-66309: Remove flakey asserts in sharded lookup test
Branch: master
https://github.com/mongodb/mongo/commit/5555653584fe0d594583267aa81805c602bc2db5

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 (SERVER-60771), but maybe something has happened recently to increase the amount of logging. Either way, as part of this ticket I'll look into ways to refactor the test so it's not so fragile; ideally the test success shouldn't depend on the amount of logging done.

Generated at Thu Feb 08 06:05:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.