[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:
Depends
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: SERVER-26768 Don't assert on collection drop in eval tests

Previously, some evalX.js tests would assert that a drop returned true,
meaning the collection existed. This may not true if two of these
tests are run concurrently in the parallel suite, so these tests should
not assert that the drop returns true.
Branch: master
https://github.com/mongodb/mongo/commit/7d7111b52e2e03b23e8357366c6b0ad02ea2ae8d

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