Closed Bug 1717445 Opened 3 years ago Closed 3 years ago

Permanent Btime failures when Gecko 91 merges to Beta on 2021-07-12

Categories

(Testing :: Raptor, defect, P1)

Firefox 91
defect

Tracking

(firefox-esr78 unaffected, firefox89 unaffected, firefox90 unaffected, firefox91 verified)

VERIFIED FIXED
91 Branch
Tracking Status
firefox-esr78 --- unaffected
firefox89 --- unaffected
firefox90 --- unaffected
firefox91 --- verified

People

(Reporter: dluca, Assigned: sparky)

References

Details

Attachments

(1 file)

Last successful run was on June 8th. Bug 1712958 is responsible for not reliable scheduling it.

I will manually add a browsertime task to the central-as-beta simulations between this last good one and today's to identify when it started.

See Also: → 1712958

Affected pushlog. Greg, this looks like a regression from bug 1708760.

Flags: needinfo?(gmierz2)
Severity: -- → S1
Priority: -- → P1
Whiteboard: [perftest:triage]

If we need to fix this quickly, we could remove the --conditioned-profile=settled from the command line used to run the tests. This would revert to using a fresh profile and settling the browser rather than conditioning a profile first. It's unlikely we'll be able to investigate this in the next couple of weeks.

Whiteboard: [perftest:triage]

:aryx, is there a way that I could run this central-as-beta simulation locally? I think there's something in condprof that's branch-specific.

Flags: needinfo?(gmierz2) → needinfo?(aryx.bugmail)

Documentation how to run these simulations can be found here. The shippable builds are different and complicated to reproduce locally - please try 'opt' instead of shippable if there are issues.

Flags: needinfo?(aryx.bugmail)

So I managed to reproduce the failure locally. Looking at the geckodriver logs and I'm seeing this error:

FATAL ERROR: Non-local network connections are disabled and a connection attempt to location.services.mozilla.com (54.186.138.163) was made.
You should only access hostnames available via the test networking proxy (if running mochitests) or from a test-specific httpd.js server (if running xpcshell tests). Browser services should be disabled or redirected to a local server.

FWIW, here's the method I used to reproduce it:

  1. Update mozilla-central to update to the parent revision that central-as-beta simulation is running on.
  2. Import the central-as-beta simulation patch from the try run.
  3. Download the binary being used in the failing tests.
  4. Run the command from the test that is failing with --binary pointing to the downloaded Firefox binary.

Patch incoming.

This patch enables non-local connections when we are running condprof to obtain a conditioned profile. The only reason these connections are being disabled to begin with is because of the web-extension we use. This fixes an issue with using the condprofs in release builds such as beta.

Assignee: nobody → gmierz2
Status: NEW → ASSIGNED
Pushed by gmierz2@outlook.com:
https://hg.mozilla.org/integration/autoland/rev/da8e89133218
Allow non-local connections when running condprof. r=perftest-reviewers,AlexandruIonescu
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: