"testr run" uses system testr to load
Bug #613129 reported by
Jonathan Lange
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Testrepository |
Fix Released
|
Wishlist
|
Robert Collins | ||
Bug Description
When hacking on testrepository, "testr run" does this: python -m subunit.run testrepository.
Of course, unless you have the current working directory in your path, then "testr load" will run the system testr. This is confusing.
| tags: | added: testr-run |
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
| Changed in testrepository: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
Revision history for this message
| Robert Collins (lifeless) wrote | #2 |
| Changed in testrepository: | |
| assignee: | nobody → Robert Collins (lifeless) |
| milestone: | none → next |
| status: | Triaged → Fix Committed |
| Changed in testrepository: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I can certainly see that. Note that testr run on testr itself is *not meant* to use the cwd testr - its meant to use the system one as a known-good baseline.