1628649 - Intermittent Chrome raptor-perftest Critical: Connection to Raptor webextension failed!

Status: RESOLVED DUPLICATE of bug 1632194

(Testing :: Raptor, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: hskupin [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=296926906&repo=try
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/EjiWsui3TWG0t1QfcDnm6A/runs/0/artifacts/public/logs/live_backing.log

---

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

I assume that Chrome didn't correctly start-up and was hung:

[task 2020-04-09T10:22:11.516Z] 10:22:11     INFO -  raptor-webext-desktop Info: starting chrome
[task 2020-04-09T10:22:11.516Z] 10:22:11     INFO -  Application command: /usr/bin/google-chrome --user-data-dir=/tmp/tmp2QBdk_.mozrunner --profile-directory=Default --no-first-run --use-mock-keychain --no-default-browser-check --proxy-server=127.0.0.1:52392 --proxy-bypass-list=localhost;127.0.0.1 --ignore-certificate-errors --load-extension=/home/cltbld/tasks/task_1586425711/build/tests/raptor/raptor/webextension/../../webext/raptor
[task 2020-04-09T10:24:28.663Z] 10:24:28 CRITICAL -  raptor-perftest Critical: Connection to Raptor webextension failed!

Comment 2

[Intermittent Failures Robot]

1 failures in 4823 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• try: 1

Platform breakdown:

• linux64-shippable: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1628649&startday=2020-04-06&endday=2020-04-12&tree=all

Comment 3

[Intermittent Failures Robot]

2 failures in 4528 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-central: 2

Platform breakdown:

• android-hw-g5-7-0-arm7-api-16: 1
• linux64-shippable: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1628649&startday=2020-04-13&endday=2020-04-19&tree=all

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Greg, do you have an idea how to get more logs out of Chrome for the startup?

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+1]]

I even wonder if that is a crash of Chrome. Lets see if my patch on bug 1630037 will help here.

Comment 6

[Greg Mierzwinski [:sparky]]

We shouldn't bother with the failures on chrome/chromium (these are very low frequency failures) unless they are permafails or nearly permafails (in that case, we downgrade the chromium/chrome version). There are non-chrome/chromium failures being mixed in this bug by the way: https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?startday=2019-12-24&endday=2020-04-22&tree=all&bug=1628649

Comment 7

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Looks like this is indeed caused by crashes of Chrome. See the try build for my patch on bug 1630037. Once landed it will turn into bug 1632194.

Comment 8

[Intermittent Failures Robot]

7 failures in 5582 pushes (0.001 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-central: 7

Platform breakdown:

• linux64-shippable: 4
• macosx1014-64-shippable: 1
• windows10-64-ref-hw-2017: 2

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1628649&startday=2020-04-20&endday=2020-04-26&tree=all

Comment 9

[Henrik Skupin [:whimboo][⌚️UTC+1]]

No more failures (beside the one mis-classified one from yesterday) which show this failure. It should be all bug 1632194 now.