[SERVER-71050] s_query_test sporadically fails on "!response.getPostBatchResumeToken()->isEmpty()" invariant Created: 03/Nov/22  Updated: 16/Jan/23  Resolved: 16/Jan/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Alexander Ignatyev Assignee: Ivan Fefer
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-72780 s_query_test ResultsMergerTestFixture... Closed
Operating System: ALL
Sprint: QE 2022-11-28, QE 2022-12-12, QE 2022-12-26, QE 2023-01-09, QE 2023-01-23
Participants:
Linked BF Score: 5

 Description   

[cpp_unit_test:s_query_test] | 2022-10-28T17:08:29.601Z I TEST 20165 [main] "child","attr":\{"json":{"t":{"$date":"2022-10-28T17:08:29.601Z"},"s":"F","c":"ASSERT","id":23079,"ctx":"main","msg":"Invariant failure","attr":\{"expr":"!response.getPostBatchResumeToken()->isEmpty()","file":"src/mongo/s/query/async_results_merger.cpp","line":631}}}

 



 Comments   
Comment by Ivan Fefer [ 16/Jan/23 ]

The failure in the ticket is part of a successful death tests. 
Tests continue to run until they hit ShouldBeInterruptibleDuringBlockingNext test that can sometimes hang and cause timeout.

Marking it as a duplicate for a ticket to fix hanging test

Comment by Ivan Fefer [ 16/Jan/23 ]

Closing this ticket as the real reason why this tests fail is SERVER-72780

Comment by Ivan Fefer [ 13/Jan/23 ]

Confirmed that this error is a part of normal test workflow: https://github.com/mongodb/mongo/blob/master/src/mongo/s/query/async_results_merger_test.cpp#L1539

The real reason for failures is SERVER-72780

Comment by Mohammad Dashti (Inactive) [ 12/Jan/23 ]

Ivan, thanks for the comment. As per our Slack discussion, assigned this ticket to you.

Comment by Ivan Fefer [ 12/Jan/23 ]

And the tests actually failing because of some deadlock in ResultsMergerTestFixture.ShouldBeInterruptibleDuringBlockingNext.

I am investigating it in SERVER-72780

Comment by Ivan Fefer [ 12/Jan/23 ]

I think this is actually not a failure, because it is always followed by 

[cpp_unit_test:s_query_test] | 2022-10-27T20:06:00.830Z I  TEST     5042603 [main] "Death test test died as expected"
[cpp_unit_test:s_query_test] | 2022-10-27T20:06:00.830Z I  TEST     5042602 [main] "Death test finishing" 

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