wireprotov2: change how revisions are specified to changesetdata Right now, we have a handful of arguments for specifying the revisions whose data should be returned. Defining how all these arguments interact when various combinations are present is difficult. This commit establishes a new, generic mechanism for specifying revisions. Instead of a hodgepodge of arguments defining things, we have a list of dicts that specify revision selectors. The final set of revisions is a union of all these selectors. We implement support for specifying revisions based on: * An explicit list of changeset revisions * An explicit list of changeset revisions plus ancestry depth * A DAG range between changeset roots and heads If you squint hard enough, this problem has already been solved by revsets. But I'm reluctant to expose revsets to the wire protocol because that would require servers to implement a revset parser. Plus there are security and performance implications: the set of revision selectors needs to be narrowly and specifically tailored for what is appropriate to be executing on a server. Perhaps there would be a way for us to express the "parse tree" of a revset query, for example. I'm not sure. We can explore this space another time. For now, the new mechanism should bring sufficient flexibility while remaining relatively simple. The selector "types" are prefixed with "changeset" because I plan to add manifest and file-flavored selectors as well. This will enable us to e.g. select file revisions based on a range of changeset revisions. Differential Revision: https://phab.mercurial-scm.org/D4979

     1

from __future__ import absolute_import, print_function

     2

     3

import unittest

     4

     5

class TestResult(unittest._TextTestResult):

     6

     7

    def __init__(self, options, *args, **kwargs):

     8

        super(TestResult, self).__init__(*args, **kwargs)

     9

        self._options = options

    10

    11

        # unittest.TestResult didn't have skipped until 2.7. We need to

    12

        # polyfill it.

    13

        self.skipped = []

    14

    15

        # We have a custom "ignored" result that isn't present in any Python

    16

        # unittest implementation. It is very similar to skipped. It may make

    17

        # sense to map it into skip some day.

    18

        self.ignored = []

    19

    20

        self.times = []

    21

        self._firststarttime = None

    22

        # Data stored for the benefit of generating xunit reports.

    23

        self.successes = []

    24

        self.faildata = {}

    25

    26

    def addFailure(self, test, reason):

    27

        print("FAILURE!", test, reason)

    28

    29

    def addSuccess(self, test):

    30

        print("SUCCESS!", test)

    31

    32

    def addError(self, test, err):

    33

        print("ERR!", test, err)

    34

    35

    # Polyfill.

    36

    def addSkip(self, test, reason):

    37

        print("SKIP!", test, reason)

    38

    39

    def addIgnore(self, test, reason):

    40

        print("IGNORE!", test, reason)

    41

    42

    def onStart(self, test):

    43

        print("ON_START!", test)

    44

    45

    def onEnd(self):

    46

        print("ON_END!")

    47

    48

    def addOutputMismatch(self, test, ret, got, expected):

    49

        return False

    50

    51

    def stopTest(self, test, interrupted=False):

    52

        super(TestResult, self).stopTest(test)