[SERVER-42102] MongoDB failed to run two test suites due to received a StopExecution exception: C++ unit test build\opt\mongo\db\pipeline\db_pipeline_test.exe failed with MSVC on windows Created: 08/Jul/19 Updated: 14/Aug/19 Resolved: 14/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Build |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | LinGao | Assignee: | Andrew Morrow (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
VS 2017 + Windows Server 2016 + MongoDB master branch latest revision |
||
| Attachments: |
|
||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | Reproduce steps:
Acutal result:
|
||||||||||||||||||||||||||||||||||
| Sprint: | Dev Tools 2019-07-15, Dev Tools 2019-08-12, Dev Tools 2019-08-26 | ||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||
| Description |
|
MongoDB failed to run two test suites due to received a StopExecution exception: C++ unit test build\opt\mongo\db\pipeline\db_pipeline_test.exe failed with MSVC on windows. It can be reproduced on master branch latest revision. Could you please help to take a look at this issue? Thanks in advance! |
| Comments |
| Comment by Andrew Morrow (Inactive) [ 09/Aug/19 ] |
|
spacelg - Have you re-tested with the above commit? |
| Comment by Andrew Morrow (Inactive) [ 01/Aug/19 ] |
|
spacelg - I see that you are working against the master branch, which is sometimes broken, per my comments in your other ticket. One thing I would like to know. Could you please make sure that you have pulled in this commit: https://github.com/mongodb/mongo/commit/5d5880c21a40ea6cb2b2c9d151d63cad675a3fca If not, could you please re-run your tests with that commit included? |
| Comment by LinGao [ 31/Jul/19 ] |
|
Hi Andrew, Sorry for the late reply! And now MongeDB failed again due to run db_repl_coordinator_test.exe test on release and debug configuration. Running the same as the previous steps python.exe buildscripts/resmoke.py --suites=unittests_repl --jobs=8 will report the following error: [executor:cpp_unit_test:job2] 2019-07-30T20:09:40.272-0700 db_repl_coordinator_test.exe ran in 39.99 seconds: failed.
As you said, I tried to run db_repl_coordinator_test.exe manually in command line, it run pass. I've attached failed test log and manually run db_repl_coordinator_test.exe test log. Could you please look at this? Thanks a lot.
log_x64_test_16.log |
| Comment by Andrew Morrow (Inactive) [ 16/Jul/19 ] |
|
spacelg - Were you able to try my suggestion to run the test manually outside of resmoke? We don't observe this failure on our side, so without some additional information from your side we are going to need to close this as "cannot reproduce". |
| Comment by Andrew Morrow (Inactive) [ 09/Jul/19 ] |
|
spacelg - What happens if you run that unit test binary directly by hand, rather than through resmoke? It looks like the test is failing, but then resmoke is failing while trying to report the failure. I'd like to understand the test failure first. |