[PATCH] hypothesis: handle "repository is unrelated" errors

David MacIver david at drmaciver.com
Fri Feb 26 12:37:12 EST 2016


The former. It happened with low enough probability that it hadn't
previously come up, but it did in a run earlier.

This is unfortunately the downside of this style of testing. :-(

On 26 February 2016 at 17:28, Martin von Zweigbergk <martinvonz at google.com>
wrote:

> On Fri, Feb 26, 2016 at 9:25 AM, David R. MacIver <david at drmaciver.com>
> wrote:
> > # HG changeset patch
> > # User David R. MacIver <david at drmaciver.com>
> > # Date 1456507454 0
> > #      Fri Feb 26 17:24:14 2016 +0000
> > # Node ID 9dc48c7b1f25c697cfdb84afc8d9a4304496be46
> > # Parent  9a28035d39f02fc7e03d0d376ce66998628a6877
> > hypothesis: handle "repository is unrelated" errors
> >
> > These can validly occur if the source repository has had its history
> > entirely rewritten and thus there are no longer any commits in
> > common.
>
> Does this mean that tests may be failing before this patch? Or will
> they start failing without this patch if you apply one of your future
> patches? If the latter, I'd prefer if you include this in that future
> patch.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mercurial-scm.org/pipermail/mercurial-devel/attachments/20160226/c2bd6a88/attachment.html>


More information about the Mercurial-devel mailing list