Windows 10 random hg verify errors?

[Matt Mackall]

On Wed, 2016-02-17 at 15:09 -0600, Eric Pyle wrote:
> Good news (sort of). I decided to use *msconfig* advanced options to limit
> my computer to *1 CPU*, and it seems to have made a world of (good)
> difference. I haven't encountered the random errors again, and I'm able to
> download big files and do big hg clones which were also an issue. I
> couldn't even download tortoisehg-3.5.2-x64.msi without getting Network
> error across different browsers.
> 
> Basically, when I tried cloning, mozilla-central, per Gregory Szorc's
> suggestion, I encountered the same network errors that eventually led to me
> investigating random integrity errors with hg verify issue.
> 
> One clone failed with integrity check failure:
> 
> % hg clone --verbose https://hg.mozilla.org/mozilla-central/
> > "C:\Users\pylee\Documents\ubsicap\repos\mozilla-central"
> > applying clone bundle from
> > https://hg.cdn.mozilla.net/mozilla-central/6ea654cad929c9bedd8a4161a182b6189
> > fbeae6a.gzip.hg
> > adding changesets
> > transaction abort!
> > rollback completed
> > abort: *integrity check failed* on 00changelog.i:b8802b591ce2!
> > [command returned code 255 Wed Feb 17 13:24:19 2016]

Symptomatic of hardware failure. You're probably not seeing this sort of thing
with other software because other software doesn't end-to-end cryptographically
checksum all the data in works on, so one bit errors don't cause it to explode.

> Most of the time I would get this DECRYPTION_FAILED_OR_BAD_RECORD_MAC error:
> 
> % hg clone --verbose https://hg.mozilla.org/mozilla-central/
> > "C:\Users\pylee\Documents\ubsicap\repos\mozilla-central"
> > applying clone bundle from
> > https://hg.cdn.mozilla.net/mozilla-central/6ea654cad929c9bedd8a4161a182b6189
> > fbeae6a.gzip.hg
> > adding changesets
> > adding manifests
> > transaction abort!
> > rollback completed
> > abort: error: DECRYPTION_FAILED_OR_BAD_RECORD_MAC
> > [command returned code 255 Wed Feb 17 13:34:02 2016]

Same.

Looking at the specs for your machine, I note two things:

- non-ECC RAM
- 4-core chip

I'd usually blame this on bad RAM as modern CPUs tend to have ECC on their
internal caches. But it's totally possible you have a core-specific failure or a
northbridge problem of some sort. 

-- 
Mathematics is the supreme nostalgia of our time.