Closed Bug 1760097 Opened 3 years ago Closed 2 months ago

Intermittent netwerk/test/unit/test_trr_confirmation.js | single tracking bug

Categories

(Core :: Networking: DNS, defect, P3)

defect

Tracking

()

RESOLVED FIXED
132 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr128 --- fixed
firefox130 --- wontfix
firefox131 --- wontfix
firefox132 --- fixed

People

(Reporter: jmaher, Assigned: valentin)

References

(Blocks 2 open bugs, Regression)

Details

(Keywords: intermittent-failure, intermittent-testcase, regression, Whiteboard: [necko-triaged][stockwell disable-recommended])

Attachments

(2 files, 1 obsolete file)

No description provided.

This test has been timing out on every comm-central push since last Friday. I can't see anything that changed which might be a reason why.

The timeout seems to happen here, maybe something just got slower and it needs a higher value.

(We haven't been marking them because c-c's been a mess, but now it isn't…)

Flags: needinfo?(dd.mozilla)

Valentin, can you take a look?

Flags: needinfo?(dd.mozilla) → needinfo?(valentin.gosu)

Not exactly sure why it would differ so much on thunderbird.
I'm just going to disable this on thunderbird. 🤷

Assignee: nobody → valentin.gosu
Flags: needinfo?(valentin.gosu)

We'll keep it open until we fix the root cause too.

Blocks: doh
Severity: -- → S4
Keywords: leave-open
Whiteboard: [stockwell needswork:owner] → [stockwell needswork:owner][necko-triaged]

It has a high failure rate on thunderbird for an unknown reason.

Pushed by valentin.gosu@gmail.com: https://hg.mozilla.org/integration/autoland/rev/e29f69d18a98 Disable test_trr_confirmation.js on thunderbird r=necko-reviewers,kershaw

This is very low volume and rarely happens on nightly.
Unassigning myself for now.

Assignee: valentin.gosu → nobody
Component: Networking → Networking: DNS
Keywords: leave-open
Whiteboard: [necko-triaged][stockwell unknown] → [necko-triaged][stockwell unknown][necko-monitor]
Attachment #9385976 - Attachment is obsolete: true
Whiteboard: [necko-triaged][stockwell unknown][necko-monitor] → [necko-triaged][stockwell unknown]

These permanent Linux Shippable and DevEdition xpcshell failures started for mozilla-beta after the machine type of the worker which executes the test switched from n2-standard-2 to c2-standard-4.

Valentin, could you take a look at the issue? Disabling on beta bears the risk the issue might resurface after the next merge to it from mozilla-central, or start directly on mozilla-central at some point.

Flags: needinfo?(valentin.gosu)
Keywords: regression
Regressed by: 1862675

The test was timing out, possibly because the confirmation interval could go
up to 64 seconds, while the test was only waiting for 60 seconds.
Adding a pref lets us reduce the time it takes to run the test, while
also making sure that the at least one successful attempt can execute
before the waiting time is done.

Assignee: nobody → valentin.gosu
Status: NEW → ASSIGNED

(In reply to Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout) from comment #74)

These permanent Linux Shippable and DevEdition xpcshell failures started for mozilla-beta after the machine type of the worker which executes the test switched from n2-standard-2 to c2-standard-4.

Valentin, could you take a look at the issue? Disabling on beta bears the risk the issue might resurface after the next merge to it from mozilla-central, or start directly on mozilla-central at some point.

Not sure why there was a difference between the runners, but the test was indeed racy.
I fixed the test and added a pref to make the test run a bit faster.

Flags: needinfo?(valentin.gosu)
Pushed by valentin.gosu@gmail.com: https://hg.mozilla.org/integration/autoland/rev/27fdd571d21e Add a pref for the max confirmation interval r=necko-reviewers,kershaw
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 132 Branch

Hi Valentin! Could you please check these xpcshell permanent failures from mozilla-release? Should also disable this on release?

Thank you!

Flags: needinfo?(valentin.gosu)

These permanent Linux Shippable and DevEdition xpcshell failures started for mozilla-beta after the machine type of the worker which executes the test switched from n2-standard-2 to c2-standard-4.

I think the same issue made it perma fail on release.
Disabling the test on release should be OK.

Flags: needinfo?(valentin.gosu)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: