Closed Bug 1240021 Opened 9 years ago Closed 9 years ago

Fennec nightly channel hasn't updated since Jan13

Categories

(Release Engineering :: Release Requests, defect)

Product:
Release Engineering
Component:
Release Requests
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: kats, Unassigned)

Details

Fennec nightly isn't finding updates, it's stuck on Jan13. Going to the folder pointed to by nightly.m.o also shows a build from jan 13, but if you navigate around on archive.m.o you can find at least one newer build from jan 14, it looks like. There are folders for jan15 but they only contain build logs and not actual apks.
hmm, is this auroranightly or nightly (central)? if you are using an OS that is based between api 11-14 (essentially honeycomb and the initial version of icecream), you should no longer be receiving updates. We are currently removing api-11+ from the platform name. poking update server, current nightly points to: http://download.cdn.mozilla.net/pub/mobile/nightly/2016/01/2016-01-15-05-53-28-mozilla-central-android-api-11/ while archive.m.o (initial download) I see: https://archive.mozilla.org/pub/mobile/nightly/latest-mozilla-central-android-api-11/ which has jan 15th, 46 gecko based apks I could easily be overlooking something so please bear with me.
I filed this about central, on api 14+ device. But, it might be working ok now. I noticed a few hours after I filed this bug that some of the builds (e.g. the one at [1]) appeared when it wasn't there before). I'm not sure what timezone that file listing is in but it might corroborate my story. I've since updated my nightly manually to today's nightly, so I can't verify. We can close this for now and if tomorrow's nightly doesn't show up properly I can reopen this bug. If there's anything in particular you want me to look for (assuming it happens again) please let me know. [1] http://download.cdn.mozilla.net/pub/mobile/nightly/2016/01/2016-01-15-05-53-28-mozilla-central-android-api-11/
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
I got the update for jan 16 so things seem to be OK now.
You need to log in before you can comment on or make changes to this bug.