Closed Bug 960495 Opened 6 years ago Closed 6 years ago

Release Mozmill 2.0.4

Categories

(Testing Graveyard :: Mozmill, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

(Whiteboard: [mozmill-2.0.4+])

Attachments

(1 file)

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.
Depends on: 960496
Depends on: 794020
Depends on: 950227
Depends on: 960976
Depends on: 960084
Blocks: 958126
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.
Blocks: 962514
No longer blocks: 962514
Blocks: 962514
Depends on: 964318
Depends on: 964751
Depends on: 964753
Depends on: 965183
No longer depends on: 794020
No longer depends on: 960421
No longer depends on: 965183
Depends on: 965183
Depends on: 965343
Depends on: 965714
Depends on: 948912
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.
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)
Depends on: 966234
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.
Blocks: 966928
No longer depends on: 966234
Depends on: 967058
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)
Depends on: 967152
Attached patch Patch v1Splinter Review
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 on attachment 8369674 [details] [diff] [review]
Patch v1

Review of attachment 8369674 [details] [diff] [review]:
-----------------------------------------------------------------

Looks good
Attachment #8369674 - Flags: review?(andrei.eftimie) → review+
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: 6 years ago
Resolution: --- → FIXED
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.