Closed Bug 1532501 Opened 6 years ago Closed 2 years ago

Intermittent browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Test timed out -

Categories

(Firefox :: Toolbars and Customization, defect, P5)

Product:
Firefox
Component:
Toolbars and Customization
Platform:
Desktop
All
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1775712

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Blocks 1 open bug)

Details

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

Attachments

(2 files)

Bug 1532501 - disable browser_toolbarButtonKeyPress.js on linux r?#intermittent-reviewers
47 bytes, text/x-phabricator-request
Details | Review
Bug 1532501 - stopgap: make browser_toolbarButtonKeyPress.js more reliable, r?jaws
48 bytes, text/x-phabricator-request
Details | Review

#[markdown(off)]
Filed by: apavel [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=231705402&repo=autoland

https://queue.taskcluster.net/v1/task/SwXOSpkyQJWoPxpTP3jzRA/runs/0/artifacts/public/logs/live_backing.log

[task 2019-03-04T19:37:51.822Z] 19:37:51 INFO - TEST-START | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js
[task 2019-03-04T19:38:36.854Z] 19:38:36 INFO - TEST-INFO | started process screentopng
[task 2019-03-04T19:38:37.458Z] 19:38:37 INFO - TEST-INFO | screentopng: exit 0
[task 2019-03-04T19:38:37.458Z] 19:38:37 INFO - Buffered messages logged at 19:37:51
[task 2019-03-04T19:38:37.459Z] 19:38:37 INFO - Entering test bound setPref
[task 2019-03-04T19:38:37.460Z] 19:38:37 INFO - Leaving test bound setPref
[task 2019-03-04T19:38:37.461Z] 19:38:37 INFO - Entering test bound testAppMenuButtonPress
[task 2019-03-04T19:38:37.463Z] 19:38:37 INFO - Console message: [JavaScript Warning: "Key event not available on some keyboard layouts: key=“r” modifiers=“accel,alt” id=“key_toggleReaderMode”" {file: "chrome://mochikit/content/tests/SimpleTest/EventUtils.js" line: 869}]
[task 2019-03-04T19:38:37.464Z] 19:38:37 INFO - Console message: [JavaScript Warning: "Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox”" {file: "chrome://mochikit/content/tests/SimpleTest/EventUtils.js" line: 869}]
[task 2019-03-04T19:38:37.465Z] 19:38:37 INFO - Buffered messages finished
[task 2019-03-04T19:38:37.466Z] 19:38:37 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Test timed out -
[task 2019-03-04T19:38:37.468Z] 19:38:37 INFO - GECKO(1536) | MEMORY STAT vsizeMaxContiguous not supported in this build configuration.
[task 2019-03-04T19:38:37.470Z] 19:38:37 INFO - GECKO(1536) | MEMORY STAT | vsize 1824MB | residentFast 269MB | heapAllocated 86MB
[task 2019-03-04T19:38:37.471Z] 19:38:37 INFO - TEST-OK | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | took 45047ms

Note that this is related to testAppMenuButtonPress. The fixed bug 1519226 was related to testBookmarkButtonPress.

In the last 7 days there were 36 failures associated with this bug: https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?startday=2019-09-07&endday=2019-09-14&tree=trunk&bug=1532501
Recent failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=266645125&repo=autoland&lineNumber=1152
Occurs on linux64, linux64-shippable, debug, macosx1014-64-shippable, windows10-64, windows10-64, windows10-64-qr debug, asan and opt build types.

:dao, can you please assign someone to take a look at this?

Flags: needinfo?(dao+bmo)

(In reply to Daniel Varga [:dvarga] from comment #21)

:dao, can you please assign someone to take a look at this?

I don't manage engineers, but I'll forward this to Jamie who wrote this test and Gijs who reviewed it.

Flags: needinfo?(jteh)
Flags: needinfo?(gijskruitbosch+bugs)
Flags: needinfo?(dao+bmo)

Looking at the logs and the test, this is the first test in this directory, and this task that is timing out is the first task in the test file. The screenshots show that the app menu popup does not show up, so presumably waiting for the popupshown event is timing out.

If this is frequent enough, it may be debuggable by doublechecking we call the relevant show/openPopup call with some debug logging, as well as adding nsTraceRefcnt::WalkTheStack(stderr) or similar into https://searchfox.org/mozilla-central/rev/dafa68a84f01897c8cfb4bbaf6829cae8df4eb57/layout/xul/nsXULPopupManager.cpp#879 (for popups where the nsIContent passed in matches the ID of the app menu popup). Effectively, it looks like we're not opening the app menu popup successfully. Because this test runs as the first test in a directory/manifest, and thus no other tests have run against Firefox before this, I'm not sure what'd cause any delayed focus or window activation events which trigger popup hiding here (which, IME, is usually what breaks popups/panels showing up). Neil, do you have ideas?

Flags: needinfo?(gijskruitbosch+bugs) → needinfo?(enndeakin)

That sounds like a start. Add some logging to break down whether the issue is that we don't get to the point of asking the popup to open, or the popup is failing to show, or whether the popup is showing then hiding again.

Adding logging to the beginning and end of nsXULPopupManager::MayShowPopup would handle both the first two cases, and logging to HidePopup for the last case. It would likely be helpful to add some logging permanently(the kind that appears in MOZ_LOG)

However, looking at the logs, the linux logs fail differently than the windows/mac ones. Some (but not all) of the linux logs have:

JavaScript error: resource:///modules/PanelMultiView.jsm, line 1225: TypeError: mainPanelView is undefined

just before it fails in the testAppMenuButtonPress test.

The mac failures appeared recently and fail at testSendTabToDeviceButtonPress instead. I suspect those are a different issue that the linux one.

Flags: needinfo?(enndeakin)

This has 137 total failures in the last thirty days and it's now on disable-recommended list: https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?startday=2019-08-22&endday=2019-09-21&tree=trunk&bug=1532501
It fails across all platforms and mostly on opt builds. Recent failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=263000352&repo=autoland
Neil, do you have any updates here or can we proceed to disable the test?

Flags: needinfo?(enndeakin)

Out of 64 failures reported for the last week when checking this, I see 50 on mac - and of the last 10 that I checked, all get stuck in testSendTabToDeviceButtonPress, and their logs contain [task 2019-09-18T18:31:02.627Z] 18:31:02 INFO - GECKO(1681) | 1568831462616 Sync.ErrorHandler ERROR Sync encountered a login error and a stack like this:

[task 2019-09-18T12:31:17.790Z] 12:31:17     INFO - Console message: [JavaScript Error: "Sync encountered an error - see about:sync-log for the log file." {file: "resource://services-sync/policies.js" line: 1005}]
[task 2019-09-18T12:31:17.790Z] 12:31:17     INFO - resetFileLog@resource://services-sync/policies.js:1005:10
[task 2019-09-18T12:31:17.790Z] 12:31:17     INFO - async*observe@resource://services-sync/policies.js:914:14
[task 2019-09-18T12:31:17.790Z] 12:31:17     INFO - observe@resource://services-common/observers.js:135:21
[task 2019-09-18T12:31:17.790Z] 12:31:17     INFO - notify@resource://services-common/observers.js:87:18
[task 2019-09-18T12:31:17.790Z] 12:31:17     INFO - notify@resource://services-sync/util.js:204:19
[task 2019-09-18T12:31:17.790Z] 12:31:17     INFO - WrappedNotify@resource://services-sync/util.js:214:17
[task 2019-09-18T12:31:17.791Z] 12:31:17     INFO - async*WrappedLock@resource://services-sync/util.js:166:27
[task 2019-09-18T12:31:17.791Z] 12:31:17     INFO - WrappedCatch@resource://services-sync/util.js:133:27
[task 2019-09-18T12:31:17.791Z] 12:31:17     INFO - login@resource://services-sync/service.js:995:66
[task 2019-09-18T12:31:17.791Z] 12:31:17     INFO - sync/<@resource://services-sync/service.js:1275:26
[task 2019-09-18T12:31:17.791Z] 12:31:17     INFO - WrappedCatch@resource://services-sync/util.js:133:27
[task 2019-09-18T12:31:17.791Z] 12:31:17     INFO - sync@resource://services-sync/service.js:1283:7
[task 2019-09-18T12:31:17.791Z] 12:31:17     INFO - async*populateSendTabToDevicesView/<@chrome://browser/content/browser-sync.js:335:29

The 4 windows failures in that window are the same; the Linux failures seem to be different.
This indicates the popup refused to open because sync broke. Mark or Edouard, can you or someone else familiar with sync take a look, and see if recent changes might explain this (e.g. bug 1579445 which landed recently and touched some of these files) ?

Flags: needinfo?(markh)
Flags: needinfo?(eoger)

The trypushes seem to all be green (including one off central rev 46ca31fd6a72 with no other changes), which makes very little sense considering the frequency of the orange... Anyway, hopefully the folks familiar with sync/fxa have some ideas here based on the failure messages.

Bug 1579445 certainly sounds like a candidate! If that's the case a fix should be trivial - sadly I couldn't quite get the fancy fuzzy try syntax working, so https://treeherder.mozilla.org/#/jobs?repo=try&revision=a6c2a25de897d60cc6811dbd0d01dd3f4f2f8384 isn't as efficient as it could be - I'll do some retriggers in my morning.

Whiteboard: [stockwell disable-recommended] → [stockwell needswork:owner]

I opened bug 1583414 to avoid syncing in this case. The try above looks greener, but not completely green - I suspect that patch will take this bug back to the frequency it was a month or so ago.

Flags: needinfo?(enndeakin)

Looks like Mark took care of this. Thanks!

Flags: needinfo?(eoger)

So I think bug 1583414 changed the severity of this even though it probably didn't fix it. Cosmin, I suspect there's no need to disable this test now, so could you please make whatever flag etc updates are necessary to reflect that?

Flags: needinfo?(markh)
Flags: needinfo?(jteh)
Flags: needinfo?(csabou)

Mark, thank you.

Flags: needinfo?(csabou)
Whiteboard: [stockwell needswork:owner] → [stockwell fixed:other]

In the last 7 days there have been 29 occurrences on Linux 64, build types asan, debug and opt.

Recent failure: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=272348177&repo=autoland&lineNumber=1830

Update:
There have been 36 failures within the last 7 days:

  • 1 failure on Windows 10 x64 asan
  • 2 failures on OS X 10.14 debug
  • 12 failures on Linux x64 shippable opt
  • 21 failures on Linux x64 opt/debug/asan

Recent failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=276557410&repo=autoland&lineNumber=2304

Flags: needinfo?(dao+bmo)
Whiteboard: [stockwell fixed:other] → [stockwell fixed:other][stockwell needswork:owner]

Dao do you have any updates here?

Flags: needinfo?(dao+bmo)
Whiteboard: [stockwell fixed:other][stockwell needswork:owner] → [stockwell needswork:owner]
Flags: needinfo?(dao+bmo)

Joel, how to proceed here?

Flags: needinfo?(jmaher)

please disable the test on linux

Flags: needinfo?(jmaher)
Flags: needinfo?(dao+bmo) → needinfo?(markh)
Assignee: nobody → apavel
Keywords: leave-open
Whiteboard: [stockwell needswork:owner] → [stockwell disabled]
Pushed by apavel@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6d315f2f77c8 disable browser_toolbarButtonKeyPress.js on linux r=jmaher

FWIW, there doesn't appear to be anything sync or fxa related in the most recent failure logs.

Flags: needinfo?(markh)
Component: Keyboard Navigation → Toolbars and Customization

Update:

There have been 32 failures within the last 7 days:

  • 1 failure on OS X 10.14 WebRender debug
  • 27 failures on Windows 10 x64 asan/debug
  • 4 failures on Windows 10 x64 WebRender debug

Recent failure log: https://treeherder.mozilla.org/logviewer?job_id=336088022&repo=mozilla-central&lineNumber=6994

[task 2021-04-10T22:24:18.084Z] 22:24:18 INFO - TEST-PASS | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Location changed after forward button pressed -
[task 2021-04-10T22:24:18.084Z] 22:24:18 INFO - Leaving test bound testBackForwardButtonPress
[task 2021-04-10T22:24:18.084Z] 22:24:18 INFO - Entering test bound testSendTabToDeviceButtonPress
[task 2021-04-10T22:24:18.084Z] 22:24:18 INFO - Leaving test bound testSendTabToDeviceButtonPress
[task 2021-04-10T22:24:18.084Z] 22:24:18 INFO - Entering test bound testReloadButtonPress
[task 2021-04-10T22:24:18.085Z] 22:24:18 INFO - Buffered messages finished
[task 2021-04-10T22:24:18.085Z] 22:24:18 INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Test timed out -
[task 2021-04-10T22:24:18.085Z] 22:24:18 INFO - GECKO(8508) | MEMORY STAT | vsize 2104294MB | vsizeMaxContiguous 67735343MB | residentFast 290MB | heapAllocated 85MB
[task 2021-04-10T22:24:18.085Z] 22:24:18 INFO - TEST-OK | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | took 90093ms

Gijs, as the owner of this component, could you please help us assign this to someone?
Thank you.

Flags: needinfo?(gijskruitbosch+bugs)
Whiteboard: [stockwell disabled] → [stockwell disabled][stockwell needswork:owner]

I tried looking at this but am not getting anywhere. It doesn't fail for me on Windows debug or opt, even with verify, even verify + fission. I then tried downloading an asan build from treeherder and running against that (as it's basically permafail on asan builds), but the asan build refuses to start (I get a dialog window with "The application was unable to start correctly (0xc0000142). Click OK to close the application."). I can't even get those builds to bring up the profile manager. So I don't know how to make any progress diagnosing what is happening or how to fix it. :decoder, can you help? Why won't asan builds start (I downloaded and unzipped the build from this task in case it matters). I'm running Win10, 32gb of RAM, Windows Dev build 21354.1 .

In the meantime I'll try a trypush with just asan win10 and some diagnostics in the test but debugging via try is super slow and atm I don't have a lot of clues about what's going on...

Flags: needinfo?(gijskruitbosch+bugs) → needinfo?(choller)

https://treeherder.mozilla.org/jobs?repo=try&selectedTaskRun=cJ6ZftfjSG-R1By2aVFTaA.0&revision=d276d9a5e8e48e22fbe3513a0fff1305ce1db10f - it's actually only failing about 1/4 or 1/3 runs, but another test in the same dir is also failing 1/3 runs or so. But as I can't run the builds I can't repro locally.

I added logging and the reload command is not firing which is why the load is not happening.

The screenshots seem to indicate that the reload button is not focused succesfully. I don't know why. Edit: added some more logging to confirm, https://treeherder.mozilla.org/jobs?repo=try&revision=6d4bd2224fd8aefbd5489c26f0b7f4fae029eaf6 .

Jared, is there a pref we can flip to disable (part of) the reload/stop animation/enable/disable dance to make this more reliable?

Flags: needinfo?(jaws)
See Also: → 1535975

Yes, you can set ui.prefersReducedMotion=1 in a test to prevent the stop/reload animation.

Flags: needinfo?(jaws)

Gijs, you could try launching with FFPuppet, it is what the fuzzing framework uses. It will disable all sandboxes, create a temporary profile and collect logs for you. No guarantees but it's worth a try.

To install:

pip install ffpuppet

To launch:

ffpuppet -d <path>/firefox

Lololol, my trypush appears to have accidentally fixed it by using example.com/1 instead of example.com as the test page. I am not thrilled with this but I think I'll take it.

Flags: needinfo?(choller)
Assignee: apavel → nobody
Pushed by jwein@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/946b9cfbd46b stopgap: make browser_toolbarButtonKeyPress.js more reliable, r=jaws

There are 52 total failures in the last 7 days on

[task 2021-09-24T23:49:40.248Z] 23:49:40     INFO - TEST-START | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js
[task 2021-09-24T23:50:05.531Z] 23:50:05     INFO - GECKO(4180) | 2021-09-24 23:50:05.530 firefox[4180:64336] Persistent UI failed to open file file:///Users/cltbld/Library/Saved%20Application%20State/org.mozilla.nightly.savedState/window_1.data: No such file or directory (2)
[task 2021-09-24T23:50:25.343Z] 23:50:25     INFO - TEST-INFO | started process screencapture
[task 2021-09-24T23:50:25.463Z] 23:50:25     INFO - TEST-INFO | screencapture: exit 0
[task 2021-09-24T23:50:25.463Z] 23:50:25     INFO - Buffered messages logged at 23:49:40
[task 2021-09-24T23:50:25.464Z] 23:50:25     INFO - Entering test bound setPref
[task 2021-09-24T23:50:25.464Z] 23:50:25     INFO - Leaving test bound setPref
[task 2021-09-24T23:50:25.465Z] 23:50:25     INFO - Entering test bound testAppMenuButtonPress
[task 2021-09-24T23:50:25.465Z] 23:50:25     INFO - TEST-PASS | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Focus inside app menu after toolbar button pressed - 
[task 2021-09-24T23:50:25.466Z] 23:50:25     INFO - Leaving test bound testAppMenuButtonPress
[task 2021-09-24T23:50:25.466Z] 23:50:25     INFO - Entering test bound testAppMenuButtonWrongKey
[task 2021-09-24T23:50:25.467Z] 23:50:25     INFO - TEST-PASS | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | App menu is closed after tab - 
[task 2021-09-24T23:50:25.468Z] 23:50:25     INFO - Leaving test bound testAppMenuButtonWrongKey
[task 2021-09-24T23:50:25.468Z] 23:50:25     INFO - Entering test bound testLibraryButtonPress
[task 2021-09-24T23:50:25.469Z] 23:50:25     INFO - TEST-PASS | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Focus inside Library menu after toolbar button pressed - 
[task 2021-09-24T23:50:25.469Z] 23:50:25     INFO - Leaving test bound testLibraryButtonPress
[task 2021-09-24T23:50:25.469Z] 23:50:25     INFO - Entering test bound testDeveloperButtonPress
[task 2021-09-24T23:50:25.470Z] 23:50:25     INFO - Buffered messages logged at 23:49:41
[task 2021-09-24T23:50:25.470Z] 23:50:25     INFO - TEST-PASS | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Focus inside Developer menu after toolbar button pressed - 
[task 2021-09-24T23:50:25.471Z] 23:50:25     INFO - Leaving test bound testDeveloperButtonPress
[task 2021-09-24T23:50:25.472Z] 23:50:25     INFO - Entering test bound testDeveloperButtonWrongKey
[task 2021-09-24T23:50:25.472Z] 23:50:25     INFO - TEST-PASS | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Developer menu not open after tab - 
[task 2021-09-24T23:50:25.472Z] 23:50:25     INFO - Leaving test bound testDeveloperButtonWrongKey
[task 2021-09-24T23:50:25.473Z] 23:50:25     INFO - Entering test bound testPageActionsButtonPress
[task 2021-09-24T23:50:25.473Z] 23:50:25     INFO - TEST-PASS | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Focus inside Page Actions menu after toolbar button pressed - 
[task 2021-09-24T23:50:25.474Z] 23:50:25     INFO - Leaving test bound testPageActionsButtonPress
[task 2021-09-24T23:50:25.474Z] 23:50:25     INFO - Entering test bound testBackForwardButtonPress
[task 2021-09-24T23:50:25.475Z] 23:50:25     INFO - TEST-PASS | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Location changed after back button pressed - 
[task 2021-09-24T23:50:25.475Z] 23:50:25     INFO - TEST-PASS | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Location changed after forward button pressed - 
[task 2021-09-24T23:50:25.476Z] 23:50:25     INFO - Leaving test bound testBackForwardButtonPress
[task 2021-09-24T23:50:25.476Z] 23:50:25     INFO - Entering test bound testReloadButtonPress
[task 2021-09-24T23:50:25.477Z] 23:50:25     INFO - Buffered messages logged at 23:49:42
[task 2021-09-24T23:50:25.477Z] 23:50:25     INFO - Waiting for button to be enabled.
[task 2021-09-24T23:50:25.477Z] 23:50:25     INFO - Focusing button
[task 2021-09-24T23:50:25.478Z] 23:50:25     INFO - Pressing space on the button
[task 2021-09-24T23:50:25.478Z] 23:50:25     INFO - Waiting for load.
[task 2021-09-24T23:50:25.479Z] 23:50:25     INFO - Buffered messages finished
[task 2021-09-24T23:50:25.479Z] 23:50:25     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Test timed out - 
[task 2021-09-24T23:50:25.479Z] 23:50:25     INFO - GECKO(4180) | MEMORY STAT | vsize 7925MB | residentFast 312MB | heapAllocated 108MB
[task 2021-09-24T23:50:25.480Z] 23:50:25     INFO - TEST-OK | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | took 45111ms
[task 2021-09-24T23:50:25.480Z] 23:50:25     INFO - Not taking screenshot here: see the one that was previously logged
[task 2021-09-24T23:50:25.481Z] 23:50:25     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/keyboard/browser_toolbarButtonKeyPress.js | Found a tab after previous test timed out: https://example.com/1 - 
[task 2021-09-24T23:50:25.481Z] 23:50:25     INFO - checking window state

Gijs, can you please take a look?

Flags: needinfo?(gijskruitbosch+bugs)

TBH I'm pretty confused; the log in comment #94 suggests that the following steps happened:

  • we loaded example.com/1;
  • the reload button was enabled;
  • we focused it and pressed space;

and then we got stuck waiting for a reload to happen.

Screenshots from this failing job show that:

  • there is only one tab and it is blank
  • the reload button was disabled;
  • there is no visible focus indicator on it;

so I'm pretty lost as to what's going wrong in the test.

Some other failing test instances do show the loaded tab with enabled reload button, but still no focus indicator. Also, some show broken other stuff, like an OS bluetooth keyboard configuration window, cf. https://firefoxci.taskcluster-artifacts.net/HHmgpoAmR46S8C6NKFOSVQ/0/public/test_info/mozilla-test-fail-screenshot_7a55qxdx.png .

I don't suppose we have any clue about when this started spiking to problematic frequencies, and what might therefore have triggered this increase? The graphs for this test suggest it was something that landed on the 16th or thereabouts (the drop on the 19th appears to be because it was a Sunday so there were fewer pushes). Did the mac infra change at any point?

Severity: normal → --
Flags: needinfo?(gijskruitbosch+bugs)
OS: Unspecified → All
Priority: P5 → --
Hardware: Unspecified → Desktop

Hey jmaher, you wouldn't happen to know if something infra-y for macOS happened around Sept 16th, would you?

Flags: needinfo?(jmaher)

we did notice that some of our HDMI dongles were problematic a few weeks ago, a lotof that is fixed- other than that our infrastructure has been stable for osx 10.15.

:dhouse- is the HDMI dongle hiccups under control as much as possible?

Flags: needinfo?(jmaher) → needinfo?(dhouse)

The hdmi dongle hiccups are not under control. Sept 9th, I quarantined workers with non-1920x1080 screen resolutions (https://bugzilla.mozilla.org/show_bug.cgi?id=1668886#c29). I mistakenly thought it was a problem from the setup+install and not a problem gradually appearing on workers. Checking again today, I see more have changed to 4k resolution.

There have not been other infra changes to these workers during this time.

Flags: needinfo?(dhouse)

Huh, looks like this went away overnight since last week?

I've manually re-set the screen resolution across the macos workers a few times over the last week (while I determine how to enforce it in our configuration).
So, it is possible that the failures were from those workers.

OK, back to P5/S4 given this seems to have gone away again - please clear severity+priority and needinfo me if this rears its head again and is likely to be an issue with the test.

Severity: -- → S4
Priority: -- → P5
Whiteboard: [stockwell disabled][stockwell needswork:owner] → [stockwell unknown]
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: