1732180 - Avoid using mozprofile when target application is Chrome/Chromium

Status: RESOLVED FIXED

(Testing :: Raptor, task, P2)

Description

[Kimberly Sereduck :kimberlythegeek]

When the correct chromedriver is not available, these failures are filed with a bug description of "Cannot remove mozprofile delimiters" causing extended investigation time, when the relevant error message is "Cannot find the chromedriver for the chrome version being tested"

Avoid using mozprofile altogether when we are running tests against Chrome/Chromium

Comment 1

[Greg Mierzwinski [:sparky]]

:kimberlythegeek, can you file a JIRA ticket for this?

Comment 2

[Kash Shampur [:kshampur] ⌚EST]

hey Kimberly ni? was missing from the previous comment I think!
Did you by chance already file a Jira for this?

Comment 3

[Kimberly Sereduck :kimberlythegeek]

https://mozilla-hub.atlassian.net/browse/FXP-2143

Comment 4

[Alexandru Ionescu (needinfo me) [:alexandrui]]

Attachment: Bug 1732180 - Avoid using mozprofile when target application is non-firefox r=#perftest

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/aeb5ae5a78c2
Avoid using mozprofile when target application is non-firefox r=perftest-reviewers,kshampur

Comment 6

[Norisz Fay [:noriszfay]]

https://hg.mozilla.org/mozilla-central/rev/aeb5ae5a78c2

Comment 7

[Pulsebot]

Backout by [e-mail]:
https://hg.mozilla.org/mozilla-central/rev/07c476c52a97
Backed out changeset aeb5ae5a78c2 for affecting the Chrome jobs and preventing getting Speedometer scores. a=backout

Comment 8

[Joel Maher ( :jmaher ) (UTC -8)]

why was this backed out? usually I see a reference to a failure.

Comment 9

[Kash Shampur [:kshampur] ⌚EST]

:jmaher it was backed out because the previous patch was failing sp3 tests on chrome android, e.g.

which was preventing us from getting speedometer scores for our dashboards

Comment 10

[Joel Maher ( :jmaher ) (UTC -8)]

can this land by itself, or is there a plan to reland the series of patches?

Comment 11

[Kash Shampur [:kshampur] ⌚EST]

as of right now the current patch can't be landed by itself (i've changed the status to needs revision to make it more clear).

is there a plan to reland the series of patches?

hmm sorry I am unclear on this - there is only one patch here, where is the series of patches? were more commits backed out when this was backed out? (doesn't look like it...)

or maybe I misunderstood - when ready again, it can be landed by itself (because afaik there is nothing else in the series?)

Comment 12

[Joel Maher ( :jmaher ) (UTC -8)]

the series I was referring to was the previous patch that was backed out for failing sp3. It sounds like this patch could be landed now with no concerns

Comment 13

[Alexandru Ionescu (needinfo me) [:alexandrui]]

I am waiting on code review for this one.

Comment 14

[Alexandru Ionescu (needinfo me) [:alexandrui]]

Some failures came up on Android, I have to debug them locally and fix them.

Comment 15

[Alexandru Ionescu (needinfo me) [:alexandrui]]

Still fixing the Android failures. Issues with some errors, not sure they are from me or intermittents

Comment 16

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/a7382d4a1a05
Avoid using mozprofile when target application is non-firefox r=perftest-reviewers,kshampur

Comment 17

[Sandor Molnar[:smolnar]]

https://hg.mozilla.org/mozilla-central/rev/a7382d4a1a05