-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Tests
-
None
The following test fails on latest but only on a sharded cluster:
https://evergreen.mongodb.com/version/598375b52fbabe60be01faed
[2017/08/03 12:51:26.519] FAIL: test_insert_large_batch (test_legacy_api.TestLegacy)
[2017/08/03 12:51:26.519] ----------------------------------------------------------------------
[2017/08/03 12:51:26.519] Traceback (most recent call last):
[2017/08/03 12:51:26.519] File "/data/mci/5d802010587152bf3ac9e4670f4061e6/src/test/test_legacy_api.py", line 376, in test_insert_large_batch
[2017/08/03 12:51:26.519] 'insert 1 document', timeout=60)
[2017/08/03 12:51:26.519] File "/data/mci/5d802010587152bf3ac9e4670f4061e6/src/test/utils.py", line 315, in wait_until
[2017/08/03 12:51:26.519] raise AssertionError("Didn't ever %s" % success_description)
[2017/08/03 12:51:26.519] AssertionError: Didn't ever insert 1 document
The test fails here:
https://github.com/mongodb/mongo-python-driver/blob/85e80bc/test/test_legacy_api.py#L360-L376
After db.collection_2.insert(insert_second_fails, w=0)) there are 0 documents in the collection instead of 1.
- depends on
-
SERVER-30486 mongos rejects OP_INSERT messages that exceed 16MB
-
- Closed
-
- is related to
-
-
- Closed
-