Closed
Bug 1190371
Opened 10 years ago
Closed 10 years ago
[mozrunner] should we make mozcrash an optional dependency of mozrunner ?
Categories
(Testing :: Mozbase, defect)
Testing
Mozbase
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: parkouss, Assigned: parkouss)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
4.29 KB,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
mozrunner currently requires mozcrash, but in some cases we don't want/need it, e.g. in mozregression.
See bug 1185632 comment 3.
Should we make that dependency optional ?
| Assignee | ||
Comment 1•10 years ago
|
||
:ted, thoughts ? I *feel* that you are the right person to ask this for, but feel free to redirect the NI if it is not the case.
Flags: needinfo?(ted)
Comment 2•10 years ago
|
||
It seems like mozcrash is generally useful when running an app. The problems in that bug sound like we could work around them.
Flags: needinfo?(ted)
| Assignee | ||
Comment 3•10 years ago
|
||
Fixing this would resolve bug 1185602, (see bug 1185602 comment 7). I am not sure if we should fix mozcrash instead, but this is a workaround that would allow to not require mozcrash when installing mozrunner, and allowing to have a try/except around mozcrash import would fix the issue.
| Assignee | ||
Comment 4•10 years ago
|
||
So, asking for review - we'll see what you think of it Ted :)
Basically this makes mozcrash an optional deps for mozrunner. So:
pip install mozrunner
would not install mozcrash, but:
pip install mozrunner[crash]
will.
For in-tree code, I don't think it will change anything, we always install every mozbase dependencies I think. But this may impact out-of-the-tree code that rely on mozcrash when they install mozrunner (I don't think there is any, but not sure) - in that case they should upgrade their dependency to "mozrunner[crash]".
Comment 5•10 years ago
|
||
Comment on attachment 8664217 [details] [diff] [review]
bug-1190371.patch
Review of attachment 8664217 [details] [diff] [review]:
-----------------------------------------------------------------
I don't feel very strongly about this, so this is fine if it helps that use case. Sorry for the long review delay!
Attachment #8664217 -
Flags: review?(ted) → review+
| Assignee | ||
Comment 6•10 years ago
|
||
| Assignee | ||
Comment 7•10 years ago
|
||
Thanks Ted! Yep, that will help for mozregression - we will be able to make it work for MSYS2 on Windows 8.1 x64 (even if this version is not supported by test harnesses), and it will allow to remove the mozcrash dependency by the way.
Pushed to try, just to be sure.
| Assignee | ||
Comment 8•10 years ago
|
||
I can't push myself right now, the tree is closed.
Try is green - thanks for checkin this in!
Leave open so I can release a new mozrunner on pypi before closing the bug.
Keywords: checkin-needed,
leave-open
Keywords: checkin-needed
| Assignee | ||
Comment 11•10 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/03d53c79f7f5158587a21697ce5dfca9c3622800
Bug 1190371 - [mozrunner] bump release to 6.11. r=me
Comment 12•10 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 13•10 years ago
|
||
Released on pypi:
Submitting dist/mozrunner-6.11.tar.gz to https://pypi.python.org/pypi
Server response (200): OK
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 14•7 years ago
|
||
Removing leave-open keyword from resolved bugs, per :sylvestre.
Keywords: leave-open
You need to log in
before you can comment on or make changes to this bug.
Description
•