Closed Bug 1494398 Opened Last year Closed Last year

Mozregression will need to pass --wait-for-browser when starting Firefox on Windows

Categories

(Testing :: mozregression, enhancement)

Unspecified
Windows
enhancement
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aklotz, Assigned: aklotz)

References

Details

Attachments

(1 file)

Once we land the launcher process, mozregression won't work right on Windows unless --wait-for-browser is passed in on the command line.

That option should be completely benign on older builds, so it should be safe to pass in all the time.
Am I reading this right? Does mozregression delegate browser launching to mozrunner? If so, huzzah, we get this for free!
(In reply to Aaron Klotz [:aklotz] from comment #1)
> Am I reading this right? Does mozregression delegate browser launching to
> mozrunner? If so, huzzah, we get this for free!

Sure does: https://github.com/mozilla/mozregression/blob/master/mozregression/launchers.py#L199

Looking at searchfox, it doesn't look like the change to mozrunner has landed yet? We'll need to do that and release a new version of that library to pypi (maybe you could do that as part of the change, you only need to modify this file: https://hg.mozilla.org/mozilla-central/file/tip/testing/mozbase/mozrunner/setup.py#l10), then update mozregression to use the new dependency.

Thanks for the report.
Flags: needinfo?(aklotz)
(In reply to William Lachance (:wlach) (use needinfo!) from comment #2)
> Looking at searchfox, it doesn't look like the change to mozrunner has
> landed yet?

The mozrunner change is riding with bug 1488554 which is currently baking on autoland.

> We'll need to do that and release a new version of that library
> to pypi (maybe you could do that as part of the change, you only need to
> modify this file:
> https://hg.mozilla.org/mozilla-central/file/tip/testing/mozbase/mozrunner/
> setup.py#l10), then update mozregression to use the new dependency.

I'm happy to help here. What's the deal with this change, do you know if we use semantic versioning here? Do I just need to bump the patch level?
Depends on: 1488554
Flags: needinfo?(aklotz) → needinfo?(wlachance)
(In reply to Aaron Klotz [:aklotz] from comment #3)
> (In reply to William Lachance (:wlach) (use needinfo!) from comment #2)
> > Looking at searchfox, it doesn't look like the change to mozrunner has
> > landed yet?
> 
> The mozrunner change is riding with bug 1488554 which is currently baking on
> autoland.
> 
> > We'll need to do that and release a new version of that library
> > to pypi (maybe you could do that as part of the change, you only need to
> > modify this file:
> > https://hg.mozilla.org/mozilla-central/file/tip/testing/mozbase/mozrunner/
> > setup.py#l10), then update mozregression to use the new dependency.
> 
> I'm happy to help here. What's the deal with this change, do you know if we
> use semantic versioning here? Do I just need to bump the patch level?

Awesome, yes, I think this would technically be a new feature that doesn't break backwards compatibility. So bump the minor version (i.e. 7.0.2 -> 7.1.0).
Flags: needinfo?(wlachance)
Comment on attachment 9012365 [details]
Bug 1494398: Bump mozrunner version to 7.1.0 to reflect wait-for-browser changes; r?wlach!

William Lachance (:wlach) (use needinfo!) has approved the revision.
Attachment #9012365 - Flags: review+
Pushed by aklotz@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/073b690ff354
Bump mozrunner version to 7.1.0 to reflect wait-for-browser changes; r=wlach
Assignee: nobody → aklotz
Status: NEW → ASSIGNED
Keywords: leave-open
NI'ing myself to make the required mozregression changes and releasing mozrunner to pypi when this lands on m-c.
Flags: needinfo?(wlachance)
Released new version of mozregression which depends on the version of mozrunner with the fix. I think we're good here now.
Status: ASSIGNED → RESOLVED
Closed: Last year
Flags: needinfo?(wlachance)
Resolution: --- → FIXED
Thanks!
Keywords: leave-open
You need to log in before you can comment on or make changes to this bug.