During update testing, we ran into a failure that looks pretty bad. For win7 32bit, 56.0 downloads 57.0.3 but then doesn't apply the update. Other inconsistencies mentioned by Cornel, that could use further testing: * There seems to be an endless loop on Fx 56 (Windows 7) - the user gets the 56.0 update then it keeps receiving updates but the update is not installed. When the user selects not to receive updates and manually checks for them (from the About dialog), the update is automatically installed * we ran into this issue for Mac and Linux on 57.0.2 but now we are seeing this for Windows 7 only. Full test report: https://docs.google.com/document/d/1fVUi6qj1UgyJMSFM8kFLEEPO8QdCd16UJce3igj7KKM/edit#
status-firefox57: --- → affected
status-firefox58: --- → ?
status-firefox59: --- → ?
status-firefox-esr52: --- → ?
tracking-firefox57: --- → blocking
tracking-firefox58: --- → +
tracking-firefox59: --- → +
tracking-firefox-esr52: --- → 57+
jlund [5:32 PM] I see some 56.0->57.0.3 successful update testing via release-localtest which should be the same as cdntest: [5:32] https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32/release-mozilla-release_firefox_win32_update_verify-bm77-build1-build197.txt.gz [5:33] https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-release-win32/release-mozilla-release_firefox_win32_update_verify-bm77-build1-build187.txt.gz [5:33] that’s via automation. Can we repeat the findings by QA locally? [5:33] (I don’t have a win32 box handy) jcristau [5:34 PM] (no windows here either) I see three options: 1) someone with a win32 box installs 56.0, changes their update channel to release-cdntest and tries to apply update 2) we wait until SV has support in Las Vegas (later today) or Romania (tomorrow) 3) we take this as an acceptable risk and ship anyway
Stefan can you try and reproduce the failure?
Mozilla/5.0 (Windows NT 6.1; rv:57.0) Gecko/20100101 Firefox/57.0 I was able successfully to update to 57.0.3 (20171226083017) from Firefox 56.0 on "release-cdntest" channel using background and manual update paths on Windows 7 x86. I did not experience any issues.
Cornel added that these were intermittent failures. Several people have tried to reproduce them and weren't able to. I think we can close this issue and go ahead and ship.
Status: NEW → RESOLVED
Last Resolved: 2 months ago
Resolution: --- → WORKSFORME
status-firefox57: affected → wontfix
tracking-firefox57: blocking → +
status-firefox58: ? → unaffected
status-firefox59: ? → unaffected
status-firefox-esr52: ? → unaffected
You need to log in before you can comment on or make changes to this bug.