Closed Bug 1272381 Opened 5 years ago Closed 2 years ago

Intermittent test_user_agent_updates.html | Test timed out

Categories

(Core :: Networking, defect, P2)

defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox49 --- wontfix
firefox50 --- affected
firefox51 --- affected
firefox52 --- wontfix

People

(Reporter: RyanVM, Assigned: valentin)

Details

(Keywords: intermittent-failure, Whiteboard: [necko-next][stockwell unknown])

Attachments

(1 obsolete file)

The fix landed on m-c 6 hours ago.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1250739
That probably fixed "not overridden", but it didn't fix every possible timed out.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Valentin, could you again look at this bug?
Assignee: nobody → valentin.gosu
Whiteboard: [necko-active]
https://hg.mozilla.org/mozilla-central/rev/f9a40027649f
Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla50
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
https://hg.mozilla.org/integration/mozilla-inbound/rev/2ad25a16424e510935ea3bca7822039c51c05340
Bug 1272381 - Use chromeScript.sendSyncMessage to initialize array and avoid race in test a=testonly
https://hg.mozilla.org/mozilla-central/rev/2ad25a16424e
Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Resolution: --- → FIXED
Still not fixed. :(
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: mozilla50 → ---
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Whiteboard: [necko-active] → [necko-next]
Valentin, do you know what is going wrong in this test?

I notice it is e10s-only...not sure if that helps.
I see this has been greatly reduced about 10 days ago- lets keep track of this and assume something fixed this and we only have a slow trickle of failures going forward.

For references this is a linu32/64 e10s issue
this has picked up again in the last 2 weeks, Valentin, can you take a look at this or help find someone who has cycles to look at it?
Flags: needinfo?(valentin.gosu)
odd, it was on a downward trend when I commented on this bug
Flags: needinfo?(valentin.gosu)
Whiteboard: [necko-next] → [necko-next][stockwell unknown]
The test is still racy. I tried to do some debugging on it, but I never got anywhere.
If it starts spiking I'll find some time to look into it.
Mass wontfix for bugs affecting firefox 52.
My first guess is that 'useragent-update-complete' listener is not ready due to race condition, so that we miss the event which will leads to test timeout. This should be a harmless tweak that worth a try.
Comment on attachment 8878967 [details]
Bug 1272381 - ensure useragent-update-complete listener is added before updating prefs.

https://reviewboard.mozilla.org/r/150218/#review155110

Worth a shot. Thanks for looking into this.
Attachment #8878967 - Flags: review?(valentin.gosu) → review+
Sadly I'm still seeing the same test failure on the try push, so it is clearly not fixed. Trying to gather log first before landing any patch.
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P3 → P2
No more instances in a long time.
I think it's safe to assume reason for the orange went away.
Status: REOPENED → RESOLVED
Closed: 5 years ago2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.