error when no repository present could be nicer
Bug #530010 reported by
Jelmer Vernooij
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Testrepository |
Fix Released
|
Wishlist
|
Jonathan Lange | ||
Bug Description
Running testr in a directory without a repository gives a somewhat confusing error:
[Errno 2] No such file or directory: '/home/
It would be neater to say "No repository found in /home/jelmer/lp.". Create one by running "testr init".
Related branches
lp:~jml/testrepository/load-implies-init
- Robert Collins: Needs Information
-
Diff: 85 lines (+39/-2)2 files modifiedtestrepository/commands/load.py (+12/-1)
testrepository/tests/commands/test_load.py (+27/-1)
Revision history for this message
| Robert Collins (lifeless) wrote Re: [Bug 530010] [NEW] error when no repository present could be nicer | #1 |
| Changed in testrepository: | |
| importance: | Undecided → Wishlist |
| status: | New → Triaged |
| Changed in testrepository: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Jonathan Lange (jml) |
| Changed in testrepository: | |
| status: | In Progress → Fix Released |
| milestone: | none → next |
To post a comment you must log in.
status triaged
importance wishlist
I agree that the error can be made nicer. My decision to show the
'message' from errors only means its not /all that/ opaque, so I'm not
in a panic to fix it. If you wanted to that would be fine.
In terms of how to fix it, I'm a bit hesitant about prompting the user
to make one; there could be other things wrong: lets focus on clear
diagnostics:
"No repository found in '/home/jelmer/lp': [Errno 2] No such file or
directory: '/home/
The help and tutorials all point out how to make a new repository very
early on.
Cheers,
Rob