Mozilla/5.0 (X11; Linux x86_64; rv:53.0) Gecko/20100101 Firefox/53.0 Build ID 20170120225344 No update in the last 3 days. URL pinged (with app.update.log set to True): https://aus5.mozilla.org/update/6/Firefox/53.0a1/20170120225344/Linux_x86_64-gcc3/fr/nightly/Linux%204.4.0-57-generic%20(GTK%203.18.9%2Clibpulse%208.0.0)/NA/default/default/update.xml?force=1 is empty If I change the platform identifier in the URL for another platform, there is an update indicated in the xml sent, ex: https://aus5.mozilla.org/update/6/Firefox/53.0a1/20170120225344/WINNT_x86_64-msvc-x64/en-US/nightly/Linux%204.4.0-57-generic%20(GTK%203.18.9%2Clibpulse%208.0.0)/NA/default/default/update.xml?force=1

this bug affects both en-US and l10n builds

Probably related, there are l10N builds but no en-US builds for Linux 64 since January 20: No en-US builds since Jan. 20: https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/ We do have l10n builds for Jan. 21: https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central-l10n/

My Nightly on Android is also stuck to Jan 20. This comment in https://bugzilla.mozilla.org/show_bug.cgi?id=1332916#c2 confirms that others are experiencing this issue.

The auto-scheduling of linux/android nightlies was not implemented over the weekend. Due primarily to newly adding taskcluster based nightlies to the mix. I've just triggered a new set, and will enable the auto-scheduling now.

Pascal pinged me about *todays* nightly (the one I set to auto-schedule) and it seems its broken updates again. This is a different reason though, and is tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=1333394 (tl;dr "beetmover" is failing because it can't trace the origin of the taskgraph to the gecko tree properly. Beetmover is the name for what moves the binaries from taskcluster artifacts to archive.m.o, including renaming them from things like `target.apk` -- Balrog doesn't trigger unless beetmover finishes. ) Of course thinking on it, we have `funsize` which is what generates partial updates, that should have submitted to balrog too, n-i to Simon who maintains funsize for us to double check that it too, is working.

I can see a complete available at the originally posted update url now, taking people to the 24th: https://aus5.mozilla.org/update/6/Firefox/53.0a1/20170120225344/Linux_x86_64-gcc3/fr/nightly/Linux%204.4.0-57-generic%20(GTK%203.18.9%2Clibpulse%208.0.0)/NA/default/default/update.xml?force=1 https://aus5.mozilla.org/update/6/Firefox/53.0a1/20170123125947/Linux_x86_64-gcc3/fr/nightly/Linux%204.4.0-57-generic%20(GTK%203.18.9%2Clibpulse%208.0.0)/NA/default/default/update.xml?force=1 shows a complete and a (single!) partial for the build on the 23rd I think I see why there aren't enough partials being generated, will put in a fix.