[SERVER-22014] index_bigkeys_nofail.js triggers spurious failures when run in parallel with other tests Created: 23/Dec/15  Updated: 26/Jan/16  Resolved: 23/Dec/15

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 3.0.8
Fix Version/s: 3.0.9

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Max Hirschhorn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: QuInt E (01/11/16)
Participants:
Linked BF Score: 0

 Description   

The index_bigkeys_nofail.js test toggles the failIndexKeyTooLong failpoint, which can cause the index_bigkeys.js test to fail because an index will actually be created even when the index key length is exceeded.

A change was already committed to skip running the index_bigkeys_nofail.js test in parallel with other tests: https://github.com/mongodb/mongo/commit/a66cc2118c711caf28a823be7c79cbf1b5c0942c. The purpose of this ticket is to track backporting that change to the 3.0 branch.

Recent failures on the 3.0 branch:



 Comments   
Comment by Githook User [ 23/Dec/15 ]

Author:

{u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}

Message: SERVER-22014 Don't run index_bigkeys_nofail.js in parallel

It sets failpoints that will cause index_bigkeys.js to fail if it runs in parallel.

(cherry picked from commit a66cc2118c711caf28a823be7c79cbf1b5c0942c)
Branch: v3.0
https://github.com/mongodb/mongo/commit/d0d5ef9345b8aa423e21c6e68d7d592feeecc650

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