Closed
Bug 1355751
Opened 7 years ago
Closed 7 years ago
Firefox ui update tests for complete patch and fallback scenario hangs after a restart of Firefox
Categories
(Testing :: Firefox UI Tests, defect)
Tracking
(firefox54 fixed, firefox55 fixed)
RESOLVED
FIXED
mozilla55
People
(Reporter: whimboo, Assigned: ato)
References
Details
Attachments
(1 file)
181.02 KB,
image/png
|
Details |
I have seen this today when I tried to use the update tests to do a cross-channel update from aurora to nightly. After more investigation I can also see it for just a complete update in the fallback scenario on aurora only. After the complete mar got invalidated and Firefox restarted the failure window is shown, but Marionette doesn't seem to get initialized anymore: 1491987554382 Marionette TRACE conn6 -> [0,4463,"quitApplication",{"flags":["eRestart","eAttemptQuit"]}] 1491987554383 Marionette INFO New connections will no longer be accepted 1491987554383 Marionette TRACE conn6 <- [1,4463,null,{}] 1491987554427 Marionette DEBUG Closed connection conn6 1491987554428 Marionette WARN New connections are currently not accepted *** UTM:SVC TimerManager:registerTimer - id: telemetry_modules_ping *** UTM:SVC TimerManager:registerTimer - id: xpi-signature-verification *** AUS:SVC Creating UpdateService *** AUS:SVC readStatusFile - status: failed: 6, path: /Volumes/data/Users/henrik/Library/Caches/Mozilla/updates/var/folders/4k/sf4gz5fn3kl9hr3nd7pzbvhc0000gn/T/tmppw7Hpi/updates/0/update.status *** UTM:SVC TimerManager:registerTimer - id: browser-cleanup-thumbnails *** AUS:SVC gCanCheckForUpdates - able to check for updates *** AUS:SVC getCanApplyUpdates - able to apply updates *** AUS:SVC readStatusFile - status: failed: 6, path: /Volumes/data/Users/henrik/Library/Caches/Mozilla/updates/var/folders/4k/sf4gz5fn3kl9hr3nd7pzbvhc0000gn/T/tmppw7Hpi/updates/0/update.status *** AUS:SVC readStatusFile - status: failed: 6, path: /Volumes/data/Users/henrik/Library/Caches/Mozilla/updates/var/folders/4k/sf4gz5fn3kl9hr3nd7pzbvhc0000gn/T/tmppw7Hpi/updates/0/update.status *** AUS:SVC handleFallbackToCompleteUpdate - install of complete or only one patch offered failed. 2017-04-12 10:59:18.500 plugin-container[25625:3459433] *** CFMessagePort: bootstrap_register(): failed 1100 (0x44c) 'Permission denied', port = 0x933b, name = 'com.apple.tsm.portname' As result we hang forever. Trying to stop the tests with Ctrl+C in the terminal doesn't close Firefox. So it looks like we also lost the Firefox process. The above is not happening when we do the fallback for a partial update. Please keep in mind that we currently do not run any complete update checks in automation, so we might have missed that. I will have to do more investigation today.
Reporter | ||
Comment 1•7 years ago
|
||
Hm, the Aurora build I was using above was from March 27th. So already a bit old. After the upgrade I don't see this issue anymore. So I did a regression check to see when this got fixed. And it happened between the nightlies on aurora for 03/30 and 03/31: https://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?fromchange=437ac8a1ad2cdb94ba9b5573da06049855ea4a38&tochange=7e44e11d00308e72547bfef822d91814c5b47634 So uplifting the patches from bug 1337743 to aurora actually made this work. But we weren't able to get it uplifted to beta anymore due to the branch merge to release on Monday! Florin, I would like to make you aware that we might see this issue for ondemand beta update tests, whenever complete patches are served. I'm not sure if that issue regressed also on beta. Sorry.
status-firefox54:
--- → fixed
status-firefox55:
--- → fixed
Depends on: 1337743
Target Milestone: --- → mozilla55
Reporter | ||
Comment 2•7 years ago
|
||
This broken behavior goes back to 2016. Means its quite before the branch merge when beta became 53.0. So I don't think that there is anything else to do here, and we can be safe that beta should not be affected - given that we haven't seen those failures yet.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•7 years ago
|
Assignee: nobody → ato
You need to log in
before you can comment on or make changes to this bug.
Description
•