Closed
Bug 960495
Opened 11 years ago
Closed 11 years ago
Release Mozmill 2.0.4
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Whiteboard: [mozmill-2.0.4+])
Attachments
(1 file)
3.76 KB,
patch
|
andrei
:
review+
|
Details | Diff | Splinter Review |
A new bug fix release of mozmill is necessary to fix some remaining issues with handling application restarts in Mozmill. Those will be added as dependencies.
Assignee | ||
Comment 1•11 years ago
|
||
Because of the fix in bug 960976 we should make sure that a new mozprofile package has been released. I will wait with doing that if other issues are coming up.
Assignee | ||
Comment 2•11 years ago
|
||
So we have a single remaining bug 965714, where we are waiting of the try server results before it can be landed. Once done we will deeply test the mozmill code and most likely will be able to release this version by late tomorrow.
Assignee | ||
Comment 3•11 years ago
|
||
Andrei, the last dependent mozrunner bug has been fixed now. But I would like to wait with releasing just another mozrunner version as long as we haven't verified that all is working. Can the SV team please use the latest code from mozbase master and run our tests. Please also ensure to figure out what's wrong with the automation script and why jsbridge is failing only there. We have to get this fixed before we can release Mozmill 2.0.4. Thanks!
Flags: needinfo?(andrei.eftimie)
Comment 4•11 years ago
|
||
I've logged bug 966234 for an issue I see with the latest changes. There is a testcase attached. The issue can been seen only with with mozmill-automation (I've only tested OSX as of now). Running the full tests repository directly from mozmill does not exhibit the problem.
Comment 5•11 years ago
|
||
I should also clear the flag. All looks good. I've run tests on OSX, Windows and Linux. The only problem I've seen is bug 966234, and that does not apply to this release. We'll need to check that for 2.0.5 probably. So all good :)
Flags: needinfo?(andrei.eftimie)
Assignee | ||
Comment 6•11 years ago
|
||
There is no-one else around nowadays to review such a patch. Given that we have again no code changes but just version bumps and changeset updates, Andrei should be fine to review it.
Attachment #8369674 -
Flags: review?(andrei.eftimie)
Comment 7•11 years ago
|
||
Comment on attachment 8369674 [details] [diff] [review] Patch v1 Review of attachment 8369674 [details] [diff] [review]: ----------------------------------------------------------------- Looks good
Attachment #8369674 -
Flags: review?(andrei.eftimie) → review+
Assignee | ||
Comment 8•11 years ago
|
||
https://github.com/mozilla/mozmill/commit/8760f54ff877c7dd02552eaddc6b9ae03ad9cfe5 (hotfix-2.0) Tagged: https://github.com/mozilla/mozmill/commits/2.0.4 Pushed to pypi: Submitting dist/jsbridge-3.0.1.tar.gz to http://pypi.python.org/pypi Server response (200): OK Submitting dist/mozmill-2.0.4.tar.gz to http://pypi.python.org/pypi Server response (200): OK We are finally done!
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•8 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•