[SERVER-20527] Delete resmoke.py from the 3.0 branch Created: 21/Sep/15  Updated: 20/Jan/16  Resolved: 23/Nov/15

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.0.6
Fix Version/s: 3.0.8

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

Issue Links:
Related
is related to SERVER-20478 resmoke.py can't pass auth/*.js Closed
Backwards Compatibility: Fully Compatible
Sprint: QuInt B (11/02/15), TIG B (10/30/15), QuInt C (11/23/15), QuInt D (12/14/15)
Participants:

 Description   

Significant modifications were made to resmoke.py during the 3.1.x development cycle. This has led to confusion both internally and externally when checking out the 3.0 branch and trying to use resmoke.py.



 Comments   
Comment by Charlie Swanson [ 20/Jan/16 ]

Hi mskalick,

We are actually currently working on restructuring/moving parts of the documentation, so I'll try to make sure we update the 3.0 version of these docs during that process.

Comment by Marek Skalický [ 14/Jan/16 ]

Please update also MongoDB 3.0 documentation - https://docs.mongodb.org/v3.0/contributors/tutorial/test-the-mongodb-server/#running-javascript-tests
It still mentions resmoke.py

Comment by Githook User [ 23/Nov/15 ]

Author:

{u'username': u'visemet', u'name': u'Max Hirschhorn', u'email': u'max.hirschhorn@mongodb.com'}

Message: SERVER-20527 Remove the old version of resmoke.py.
Branch: v3.0
https://github.com/mongodb/mongo/commit/a9deb75ef4ca314e3ba59c24f8bb09699769ce9d

Comment by Max Hirschhorn [ 25/Sep/15 ]

schwerin, my original intent was to backport resmoke.py to the 3.0 branch. I liked the idea of being able to check out the v3.0 branch and not having to unlearn all the niceties of resmoke.py, even if we didn't make it the test runner that Evergreen uses (for fear of destabilization).

Doing so would require updating all the blacklists in buildscripts/resmokeconfig/suites/. They may be similar to what they were when 424314f was committed, but I'm not sure anymore. As part of SERVER-18268 we made changes to the mongo shell to support running the sharding and replication tests in parallel. We'd still be able to use the same port allocation scheme (contiguous ranges starting from 20000) for MongoDB processes started by resmoke.py without conflicting with anything, but wouldn't actually be able to run those tests in parallel on the 3.0 branch.

I think until we want to dedicate time to having someone backport resmoke.py that we should delete the existing version from the 3.0 branch because it isn't really usable.

Comment by Andy Schwerin [ 22/Sep/15 ]

Would it be challenging to backport resmoke.py to 3.0?

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