Verify error in hg:jdk/jdk
chris.hegarty at oracle.com
Thu Jul 25 11:36:58 UTC 2019
The, downstream, JDK Sandbox repository  fails to verify.
I dunno what the issue was or how hard it was to fix, but if possible
could the sandbox please be fixed?
> On 25 Jul 2019, at 00:02, Iris Clark <iris.clark at oracle.com> wrote:
> hg:jdk/jdk is now open and verifies. Even if your local repository is
> corrupt, you may continue using it. The corruption does not propagate
> via pushes, since changeset IDs are unchanged.
> I strongly advise everybody to at least understand whether their local
> repositories are corrupt. The following shows the output of the `hg
> verify` command for a corrupt repository:
> $ hg verify
> checking changesets
> checking manifests
> crosschecking files in changesets and manifests
> checking files
> test/langtools/jdk/javadoc/doclet/testLinkOption/TestOptionOrder.java at 55761: f7fb5d9b7490 not in manifests
> 184109 files, 55795 changesets, 479538 total revisions
> 1 integrity errors encountered!
> (first damaged changeset appears to be 55761)
> If you want to work with a repository which verifies, you should do a
> fresh clone of hg:jdk/jdk. Confident users can create a new repository
> by cloning the corrupt repository up to the damaged changeset (`hg clone
> -r 55760 corrupt fixed`) and then pulling the remaining changesets from
> hg:jdk/jdk (hg pull -u).
> Thank you for your patience.
> ----- Original Message -----
> From: iris.clark at oracle.com
> To: jdk-dev at openjdk.java.net
> Cc: iris.clark at oracle.com
> Sent: Wednesday, July 24, 2019 10:04:33 AM GMT -08:00 US/Canada Pacific
> Subject: Verify error in hg:jdk/jdk -- repository now READ-ONLY
> I’ve made the hg:jdk/jdk repository READ-ONLY.
> A verify error which was discovered in the repository and we’d like
> to ensure that no further changesets are pushed as a solution is investigated.
More information about the jdk-dev