Pass in --utility-path and --certificate-path to b2g mochitest mozharness script

RESOLVED INVALID

Status

Release Engineering
General
RESOLVED INVALID
5 years ago
a month ago

People

(Reporter: ahal, Assigned: ahal)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
With the refactor in bug 865349 we no longer use the super hacky hardcoded method of finding the bin/certs dirs used by automation.py.in. This means we'll have to pass them in manually via command line.
(Assignee)

Comment 1

5 years ago
Created attachment 772079 [details] [diff] [review]
Patch 1.0 - add command line paths

Pushed to ash out of an abundance of caution and waiting for results:
https://tbpl.mozilla.org/?tree=Ash&rev=099d4bccd08e
Attachment #772079 - Flags: review?(jgriffin)
Comment on attachment 772079 [details] [diff] [review]
Patch 1.0 - add command line paths

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

Seems to do the right thing, but can't tell from ash...looks like something Bad happened during the last merge.
Attachment #772079 - Flags: review?(jgriffin) → review+
(Assignee)

Comment 3

5 years ago
That ash problem got cleared up, but it looks like this patch actually is causing bustage.. sigh, https://tbpl.mozilla.org/php/getParsedLog.php?id=25039124&tree=Ash

Looks like the binaries in the utility path are either the wrong format, or the runtestsb2g.py script is using utility path in the wrong way.
(Assignee)

Comment 4

5 years ago
Comment 3 is happening because the non-patched version of runreftestb2g.py is using the utilityPath to find xpcshell: http://mxr.mozilla.org/mozilla-central/source/testing/mochitest/runtestsb2g.py#474

The refactor in bug 865349 fixes the problem (which is why I never noticed it until pushing to Ash). All this means is that this patch will need to land at the same time as bug 865349.
Product: mozilla.org → Release Engineering
(Assignee)

Comment 5

5 years ago
I ended up writing the patch in bug 865349 such that this patch was no longer needed.
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
Component: General Automation → General
Product: Release Engineering → Release Engineering
You need to log in before you can comment on or make changes to this bug.