[SERVER-29836] Running unit test test_evergreen.py requires PYTHONPATH Created: 23/Jun/17 Updated: 29/Mar/18 Resolved: 29/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jonathan Abrahams | Assignee: | Robert Guo (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | TIG 2018-04-09 | ||||||||
| Participants: | |||||||||
| Description |
|
The unit test buildscripts/tests/ciconfig/test_evergreen.py requires setting PYTHONPATH if it's invoked as
This works:
|
| Comments |
| Comment by Robert Guo (Inactive) [ 29/Mar/18 ] | |
|
Closing as a dupe of | |
| Comment by Max Hirschhorn [ 27/Jun/17 ] | |
|
We should remove the if __name__ == "__main__" logic from each of the unit tests. We can use either python -m discover ... to run the test cases from a particular directory or implement | |
| Comment by Yves Duhem [ 23/Jun/17 ] | |
|
It is possible to run the tests from the root of the repository using:
I propose removing the option to run the test_evergreen module as a script or leaving it as is (requiring the path to contain the root of the repository). |