evolve: handle a case in pubic-div when merging results in same as public In public divergence resolution, what we do is: 1) first apply content divergence resolution 2) then phase divergent resolution on resultant node of 1) case While doing case 1 it is possible that result of merging the two csets would have same changes as public one contains. And then processing the case 2 would create an empty commit which is not something we want to do. So this patch catch that same case when merging results in same as public cset and don't create a new node, instead to solve the divergence it just add a obsmarker from "other divergent" to "public divergent" i.e. [other, (public,)] Next patch will add the continue case handling for this same case. This patch also adds the tests for the different cases which are possible for the above mentioned case. There is test for continue case too which is broken in this patch and will be fixed in next patch.

     1

#!/usr/bin/env python

     2

import os

     3

import sys

     4

import subprocess

     5

     6

if len(sys.argv) < 2:

     7

    execname = os.path.basename(sys.argv[0])

     8

    print >> sys.stderr, "usage: %s CLIENT_ID" % execname

     9

    10

client_id = sys.argv[1]

    11

    12

subprocess.check_call(['hg', 'branch', "--force", "hammer-branch-%s" % client_id])

    13

    14

while True:

    15

    subprocess.check_call([

    16

        'hg', 'commit',

    17

        "--config", "ui.allowemptycommit=yes",

    18

        "--message", "hammer-%s" % client_id,

    19

    ])

    20

    nodeid = subprocess.check_output([

    21

        'hg', 'log', '--rev', '.', '--template', '{node}'

    22

    ])

    23

    subprocess.check_call([

    24

        'hg', 'debugobsolete', ''.join(reversed(nodeid)), nodeid

    25

    ])

    26

    subprocess.check_call(['hg', 'pull'])

    27

    subprocess.check_call(['hg', 'push', '--force'])