canmove, Confirmed users
6,441
edits
Releases/Firefox 40.0/BuildNotes: Difference between revisions
→beta update verify failures in chunks 3 and 4 (all platforms
No edit summary |
|||
| Line 31: | Line 31: | ||
==== beta update verify failures in chunks 3 and 4 (all platforms ==== | ==== beta update verify failures in chunks 3 and 4 (all platforms ==== | ||
Both of these are showing the "complete" block missing from update response for 39.0 release (they failures look slightly different, because chunk 3 is doing a full check, and chunk 4 is doing a quick check). | Both of these are showing the "complete" block missing from update response for 39.0 release (they failures look slightly different, because chunk 3 is doing a full check, and chunk 4 is doing a quick check). | ||
When Ben investigated this, Balrog was returning a response that included a complete and a partial, but the partial was pointing at Bouncer instead of directly at FTP. This is because the 39.0 -> 40.0 partial is shared with the release channel, so they Balrog submitter didn't submit it for Beta as well. We should fix that, and also {{bug|1170919}}. | |||
==== Mac release update verify failures ==== | ==== Mac release update verify failures ==== | ||
5 of the mac release update_verify failed with either an empty response, or completes that specified download.m.o instead of stage.m.o (despite being on the release-localtest channel). Not reproducible now, so must have been caching issues. We may need a delay at the end of the updates builder again. Also should look to see if caching is doing what we expect. | 5 of the mac release update_verify failed with either an empty response, or completes that specified download.m.o instead of stage.m.o (despite being on the release-localtest channel). Not reproducible now, so must have been caching issues. We may need a delay at the end of the updates builder again. Also should look to see if caching is doing what we expect. | ||