[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: |
|
||||
| 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: It sets failpoints that will cause index_bigkeys.js to fail if it runs in parallel. (cherry picked from commit a66cc2118c711caf28a823be7c79cbf1b5c0942c) |