[SERVER-26768] eval7.js and eval9.js conflict in parallel suite Created: 25/Oct/16 Updated: 31/Oct/16 Resolved: 25/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Charlie Swanson |
| 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: | Query 2016-10-31 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Both tests assert that they a drop of the collection test.evalprep returns true (meaning the collection existed), which might not be true if they both run concurrently (as in the parallel suite). We should change these tests to use unique collection names. |
| Comments |
| Comment by Githook User [ 25/Oct/16 ] |
|
Author: {u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'charlie.swanson@mongodb.com'}Message: Previously, some evalX.js tests would assert that a drop returned true, |