[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: Text File Manually run db_repl_coordinator_test.exe.log     Text File log_x64_test_13.log     Text File log_x64_test_15.log     Text File log_x64_test_16.log    
Issue Links:
Duplicate
is duplicated by SERVER-42101 MongoDB failed to run two test suites... Closed
Operating System: ALL
Steps To Reproduce:

Reproduce steps:
1. git clone -c core.autocrlf=true https://github.com/mongodb/mongo D:\MongoDB\src
2. Open a VS 2017 x64 command prompt and browse to D:\MongoDB\src
3. pip.exe install --user -r .\etc\pip\dev-requirements.txt
4. python.exe buildscripts/scons.py all -j4
5. python.exe buildscripts/resmoke.py --suites=unittests --jobs=1
6. python.exe buildscripts/resmoke.py --suites=unittests_query --jobs=1

 

Acutal result:

[executor:cpp_unit_test:job0] 2019-07-07T23:24:17.052-0700 db_pipeline_test.exe ran in 29890.23 seconds: failed.
[executor:cpp_unit_test:job0] 2019-07-07T23:24:17.052-0700 C++ unit test build\opt\mongo\db\pipeline\db_pipeline_test.exe failed, so stopping...
[executor:cpp_unit_test:job0] 2019-07-07T23:24:17.052-0700 Received a StopExecution exception: C++ unit test build\opt\mongo\db\pipeline\db_pipeline_test.exe failed.
[executor] 2019-07-07T23:24:17.052-0700 Waiting for threads to complete
[executor] 2019-07-07T23:24:17.052-0700 Threads are completed!
[executor] 2019-07-07T23:24:17.052-0700 Summary: 25 test(s) ran in 30041.11 seconds (24 succeeded, 64 were skipped, 1 failed, 0 errored)
 The following tests failed (with exit code):
 build\opt\mongo\db\pipeline\db_pipeline_test.exe (3221226356 UNKNOWN)
[resmoke] 2019-07-07T23:24:17.052-0700 ================================================================================
[resmoke] 2019-07-07T23:24:17.052-0700 Summary of unittests suite: 25 test(s) ran in 30041.11 seconds (24 succeeded, 64 were skipped, 1 failed, 0 errored)
The following tests failed (with exit code):
 build\opt\mongo\db\pipeline\db_pipeline_test.exe (3221226356 UNKNOWN)
25 test(s) ran in 30041.11 seconds (24 succeeded, 64 were skipped, 1 failed, 0 errored)
 cpp_unit_tests: 25 test(s) ran in 30041.11 seconds (24 succeeded, 64 were skipped, 1 failed, 0 errored)
 The following tests failed (with exit code):
 build\opt\mongo\db\pipeline\db_pipeline_test.exe (3221226356 UNKNOWN)
[resmoke] 2019-07-07T23:24:17.052-0700 Exiting with code: 1
--- Logging error ---
Traceback (most recent call last):
 File "C:\tools\python3\lib\logging\__init__.py", line 1037, in emit
 stream.write(msg + self.terminator)
 File "C:\tools\python3\lib\encodings\cp1252.py", line 19, in encode
 return codecs.charmap_encode(input,self.errors,encoding_table)[0]
UnicodeEncodeError: 'charmap' codec can't encode character '\ufffd' in position 161: character maps to <undefined>
Call stack:
 File "C:\tools\python3\lib\threading.py", line 885, in _bootstrap
 self._bootstrap_inner()
 File "C:\tools\python3\lib\threading.py", line 917, in _bootstrap_inner
 self.run()
 File "D:\MongoDB\src\buildscripts\resmokelib\core\pipe.py", line 63, in run
 self.__logger.log(self.__level, line.rstrip())
Message: '2019-07-07T15:03:54.652-0700 I ACCESS [main123456789] invalid char in key file 904a-8ef2-498f-e3c1: \ufffd\x04V'
Arguments: ()
[command took 30042 seconds]

 

 

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.
[executor:cpp_unit_test:job2] 2019-07-30T20:09:40.272-0700 C++ unit test build\opt\mongo\db\repl\db_repl_coordinator_test.exe failed, so stopping...
[executor:cpp_unit_test:job2] 2019-07-30T20:09:40.272-0700 Received a StopExecution exception: C++ unit test build\opt\mongo\db\repl\db_repl_coordinator_test.exe failed.
[executor] 2019-07-30T20:09:40.272-0700 Waiting for threads to complete
[executor] 2019-07-30T20:09:40.272-0700 Threads are completed!
[executor] 2019-07-30T20:09:40.272-0700 Summary: 3 test(s) ran in 40.00 seconds (2 succeeded, 0 were skipped, 1 failed, 0 errored)
The following tests failed (with exit code):
build\opt\mongo\db\repl\db_repl_coordinator_test.exe (17 UNKNOWN)
[resmoke] 2019-07-30T20:09:40.287-0700 ================================================================================
[resmoke] 2019-07-30T20:09:40.287-0700 Summary of unittests_repl suite: 3 test(s) ran in 40.00 seconds (2 succeeded, 0 were skipped, 1 failed, 0 errored)
The following tests failed (with exit code):
build\opt\mongo\db\repl\db_repl_coordinator_test.exe (17 UNKNOWN)
3 test(s) ran in 40.02 seconds (2 succeeded, 0 were skipped, 1 failed, 0 errored)
cpp_unit_tests: 3 test(s) ran in 40.00 seconds (2 succeeded, 0 were skipped, 1 failed, 0 errored)
The following tests failed (with exit code):
build\opt\mongo\db\repl\db_repl_coordinator_test.exe (17 UNKNOWN)
[resmoke] 2019-07-30T20:09:40.287-0700 Exiting with code: 1
[command took 41 seconds]

 

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.logManually run db_repl_coordinator_test.exe.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.

Generated at Thu Feb 08 04:59:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.