runtestremote change for --pidfile and --enablePrivilege parameters need to land on mozilla-beta

RESOLVED FIXED

Status

RESOLVED FIXED
7 years ago
7 months ago

People

(Reporter: jmaher, Assigned: jmaher)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

7 years ago
these changes are in m-c and partially on m-a, but are required for us to run jsreftests.
(Assignee)

Updated

7 years ago
tracking-firefox6: --- → ?
(Assignee)

Comment 1

7 years ago
Created attachment 533364 [details] [diff] [review]
add --pidfile and --enable-privilege to mozilla-beta for android testing (1.0)

this patch only affects android tegra testing and will enable us to run jsreftests as they are almost ready to turn on.  In addition this adds a pidfile option so we can cleanup zombie processes if they exist.
Assignee: nobody → jmaher
Attachment #533364 - Flags: review?(ctalbert)

Comment 2

7 years ago
Mozilla-beta right now is Firefox 5, re-setting flags properly.
tracking-firefox5: --- → ?
tracking-firefox6: ? → ---

Comment 3

7 years ago
Comment on attachment 533364 [details] [diff] [review]
add --pidfile and --enable-privilege to mozilla-beta for android testing (1.0)

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

These look good for m-beta.
Attachment #533364 - Flags: review?(ctalbert) → review+

Comment 4

7 years ago
Please request approvals using the attachment flag approval-mozilla-beta? and not the tracking flags. Thanks.
(Assignee)

Comment 5

7 years ago
I cannot find any flags to set related to the attachment, the only flags I see are for review, feedback, addl review.
Bleah - yeah, sorry Joel, this component doesn't have those flags available - we'll process it in tracking triage and give you an approval in comments. (Is it worth you or Clint finding out how to get the flags added to this product? Are there likely to be more bugs like this?)
(Assignee)

Comment 7

7 years ago
Thanks for the info.

I would assume there will be a few random bugs that we need to get landed across the branches, but not a large frequency.  If it isn't too difficult, it might make sense to add these flags to the testing component since we do have a lot of little harnesses and tools.  These specific bugs are because we are fine tuning the android tests and turning on jsreftests for the first time.

Comment 8

7 years ago
(In reply to comment #7)
> Thanks for the info.
> 
> I would assume there will be a few random bugs that we need to get landed
> across the branches, but not a large frequency.  If it isn't too difficult,
> it might make sense to add these flags to the testing component since we do
> have a lot of little harnesses and tools.  These specific bugs are because
> we are fine tuning the android tests and turning on jsreftests for the first
> time.

I think there will always be a couple of these on some very low frequency basis as the test harness infrastructure needs to adapt to product changes. We'll likely see most of these anytime we're bringing a new test harness online (like android).  Filed bug 659096 so we can get the proper flags setup.
Clearing the nom - discussed in triage - a=me to land wherever you need it on the assumption that it's test only and easy to back out.
tracking-firefox5: ? → ---
(Assignee)

Comment 10

7 years ago
http://hg.mozilla.org/releases/mozilla-beta/rev/23d449276096
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Component: New Frameworks → General
Product: Testing → Testing
You need to log in before you can comment on or make changes to this bug.