1380275 - Permafailure when Gecko56 move to Beta in browser_net_open_in_debugger.js | A promise chain failed to handle a rejection: [object Object] - rejection date: Mon Jul 03 2017 11:28:22 GMT+0000 (UTC) - stack: JS frame ::

Status: RESOLVED INVALID

(DevTools :: Netmonitor, defect, P3)

Description

[Carsten Book [:Tomcat]]

found during uplift simulation TEST-UNEXPECTED-FAIL | devtools/client/netmonitor/test/browser_net_open_in_debugger.js | A promise chain failed to handle a rejection: [object Object] - rejection date: Mon Jul 03 2017 11:28:22 GMT+0000 (UTC) - stack: JS frame :: resource://gre/modules/Promise.jsm -> resource://gre/modules/Promise-backend.js :: register :: line 199

link: 

https://treeherder.mozilla.org/logviewer.html#?job_id=112605223&repo=try&lineNumber=6442

seems to be perma failure in the last uplift simulation runs with m-c as beta

Comment 1

[Carsten Book [:Tomcat]]

Honza: could you take a look ? i guess this will be a perma failure after next merge day

Comment 2

[Jan Honza Odvarko [:Honza] (always need-info? me)]

How exactly could I test this?

When running the test locally on my Win10 machine with the latest m-c build, the test passes just fine.

What's different in our configs?

Honza

Comment 3

[Carsten Book [:Tomcat]]

(In reply to Jan Honza Odvarko [:Honza] from comment #2)
> How exactly could I test this?
> 
> When running the test locally on my Win10 machine with the latest m-c build,
> the test passes just fine.
> 
> What's different in our configs?
> 
> Honza

Hi Honza, either you could use https://wiki.mozilla.org/Sheriffing/Uplift-Sim with the patches in https://bugzilla.mozilla.org/show_bug.cgi?id=1280663 or my try run in https://treeherder.mozilla.org/#/jobs?repo=try&author=[e-mail]&bugfiler&noautoclassify&selectedJob=112589803

Comment 4

[Julian Descottes [:jdescottes]]

It might be related to the same root cause as https://bugzilla.mozilla.org/show_bug.cgi?id=1368931
-> new debugger frontend is not yet enabled in beta due to http://searchfox.org/mozilla-central/source/devtools/client/preferences/debugger.js#4-8 

This pref file should be updated in the 56 nightly cycle so that the new debugger frontend rides the trains.

Maybe try to force using the old debugger locally and see if you can repro the failure.

Comment 5

[Julian Descottes [:jdescottes]]

(just tried locally and flipping the debugger pref reproduces the issue on latest central)

Comment 6

[Jan Honza Odvarko [:Honza] (always need-info? me)]

Thanks for the info Julian!

When bug 1294139 lands in m-c, the next beta simulation should be ok.

Honza

Comment 7

[Gerry Chang [:gchang]]

Hi Tomcat,
bug 1294139 was already in m-c, could you check if this issue still exists?

Comment 8

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

I'll do a new batch of simulation pushes tomorrow.

Comment 9

[Liz Henry (:lizzard) (privacy/fingerprinting team)]

Since Honza is still on PTO, can one of you either try to fix this or help find an owner for the bug who can work on it today? Thanks!

Comment 10

[Liz Henry (:lizzard) (privacy/fingerprinting team)]

Patrick, maybe you can help here.

Comment 11

[Julian Descottes [:jdescottes]]

Liz: Did this failure reoccur? According to the investigation it should be fixed already, now that the new debugger is enabled in all channels. Do you have a link to try run that failed for this test on beta?

Comment 12

[Liz Henry (:lizzard) (privacy/fingerprinting team)]

Wes, or Ryan, is this fixed in 56?

Comment 13

[Wes Kocher (:KWierso) (Not reading bugmail; email directly if needed)]

I don't see this failure on the actual uplift to beta.

Comment 14

[Liz Henry (:lizzard) (privacy/fingerprinting team)]

OK great, sorry for the false alarm.

Comment 15

[Jan Honza Odvarko [:Honza] (always need-info? me)]

(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #14)
> OK great, sorry for the false alarm.
Closing 
Honza