Fix UNCOMPRESSION_FAILED (error 12) update failures |
|||
Issue descriptionUNCOMPRESSION_FAILED means that chrome.packed.7z could not be uncompressed. It is the top update failure on a single day when we are not pushing a new stable release, representing over 1/4 of all failures. chrome.packed.7z produces either the big chrome.7z (for a full update) or the smaller chrome_patch.diff (for a diff update). The vast majority of the failures are for clients requesting the full updater. We should understand why this is failing and see what we can do about it.
,
Sep 28 2016
Looking back in history a bit, this error rises quite a bit after each stable push and has a slow decay. This indicates that some clients do eventually succeed, but that population gets their updates long after they should and there's a large population that never does.
,
Sep 28 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 20 2017
Is this still an issue? If so, feel free to reopen the issue. Thanks!
,
Nov 21 2017
It's still an issue, but at this point it should be a part of a general "hunt down and kill update failures" task. Error 12 isn't necessarily the most impactful one to target at this point. |
|||
►
Sign in to add a comment |
|||
Comment 1 by grt@chromium.org
, Sep 27 2016