[SERVER-39928] Stop testing PyMongo with Python 2.6 in drivers-nightly Created: 01/Mar/19 Updated: 29/Oct/23 Resolved: 01/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0-rc5, 4.0.12, 3.4.23 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Shane Harvey | Assignee: | Ian Whalen (Inactive) |
| Resolution: | Fixed | 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 | ||||||||||||
| Backport Requested: |
v4.2, v4.0, v3.4
|
||||||||||||
| Participants: | |||||||||||||
| Description |
|
PyMongo removed support for Python 2.6 in
We need to remove 2.6 from drivers-nightly-3.4, drivers-nightly-4.0, and drivers-nightly (drivers-nightly-3.6 already doesn't use Python 2.6). CC: behackett |
| Comments |
| Comment by Githook User [ 01/Aug/19 ] |
|
Author: {'name': 'Ian Whalen', 'username': 'IanWhalen', 'email': 'ian@mongodb.com'}Message: |
| Comment by Githook User [ 31/Jul/19 ] |
|
Author: {'name': 'Ian Whalen', 'username': 'IanWhalen', 'email': 'ian@mongodb.com'}Message: |
| Comment by Ian Whalen (Inactive) [ 30/Jul/19 ] |
|
Just a note that this is not going into master to my knowledge. 4.0 commit is done. 4.2 and 3.4 are next. |
| Comment by Githook User [ 30/Jul/19 ] |
|
Author: {'name': 'Ian Whalen', 'username': 'IanWhalen', 'email': 'ian@mongodb.com'}Message: |
| Comment by Ian Whalen (Inactive) [ 11/Mar/19 ] |
|
can someone point me to where this code live? I'm happy to change and patch test this. |
| Comment by Bernie Hackett [ 11/Mar/19 ] |
|
Since this build is using the python driver toolchain, just change 2.6 to 2.7 in the interpreter path (/opt/python/2.7/bin/python). |
| Comment by Bernie Hackett [ 04/Mar/19 ] |
|
Indeed. The drivers-nightly project was created to catch driver and application breaking changes in server patch releases before the releases happen (I don't remember what the bug was that caused this project to happen, but I recall it was pretty bad). For that to work, somebody on the server team needs to be notified when tests fail. |