Closed Bug 1859836 Opened 1 year ago Closed 11 months ago

Resolve osx1300 long completion times of chrome

Categories

(Testing :: Raptor, task, P1)

Product:
Testing
Component:
Raptor
Version:
Default
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1858236

People

(Reporter: aglavic, Assigned: aglavic)

References

Details

(Whiteboard: [fxp])

Chrome is taking a long time to complete tasks on osx13 M2s, this bug is to understand exactly why that is ocuring, we found that it was taking a very long time

For context on Firefox there have been no timeouts of osx1300 for speedometer3 the past 2 months
Speedometer3 takes 50% longer to run as Speedometer on Firefox

This month speedometer3 has completed 2 times this entire October(2/11) and takes 30+ minutes

  • What I see is that regular speedometer takes ~20 min, 50% more means it'll get to ~30 min also
    Seems to be an issue with the mac chrome rather than speedometer or the macs themselves

Speedometer takes:

  • 5 minutes and 40/50 seconds per iteration on macosx1300 for chrome
  • takes 30 seconds on firefox on macosx1300
Severity: -- → S1
tracking-firefox119: --- → ?
tracking-firefox120: --- → ?
Priority: -- → P1
No longer blocks: 1858226

:aglavic is this an S1 https://firefox-source-docs.mozilla.org/bug-mgmt/guides/severity.html?
Release tracking requests are automatically added when the severity is set to S1

Flags: needinfo?(aglavic)

Removing tracking requests in the meantime

tracking-firefox119: ? → ---
tracking-firefox120: ? → ---

I'm sorry I didn't realize that I added a severity tag

Flags: needinfo?(aglavic)

I do think this is a s2 though

Severity: S1 → S2
Priority: P1 → --
Priority: -- → P1
Status: NEW → RESOLVED
Closed: 11 months ago
Duplicate of bug: 1858236
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.