killdaemons: close pid file before killing processes With #serve enabled on Windows, I was getting occasional stacktraces like this: Errored test-hgweb-json.t: Traceback (most recent call last): File "./run-tests.py", line 724, in run self.tearDown() File "./run-tests.py", line 805, in tearDown killdaemons(entry) File "./run-tests.py", line 540, in killdaemons logfn=vlog) File "...\tests\killdaemons.py", line 94, in killdaemons os.unlink(pidfile) WindowsError: [Error 32] The process cannot access the file because it is being used by another process: '...\\hgtests.zmpqj3\\child80\\daemon.pids' Adrian suggested using util.posixfile, which works. However, the 'mercurial' package isn't in sys.path when invoking run-tests.py, and it isn't clear that hacking[1] it in is a good thing (especially for test-run-tests.t, which uses an installation in a temp folder). I tried using ProcessMonitor to figure out what the other process is, but that monitoring slows things down to such a degree that the issue doesn't occur. I was ready to blame the virus scanner, but it happens without that too. Looking at the code, I don't see anything that would have the pid file open. But I was able to get through about 20 full test runs without an issue with this minor change, whereas before it was pretty certain to hit this at least once in two or three runs. [1] https://www.mercurial-scm.org/pipermail/mercurial-devel/2017-May/097907.html

     1

Issue1678: IndexError when pushing

     2

     3

setting up base repo

     4

  $ hg init a

     5

  $ cd a

     6

  $ touch a

     7

  $ hg ci -Am a

     8

  adding a

     9

  $ cd ..

    10

    11

cloning base repo

    12

  $ hg clone a b

    13

  updating to branch default

    14

  1 files updated, 0 files merged, 0 files removed, 0 files unresolved

    15

  $ cd b

    16

    17

setting up cset to push

    18

  $ hg up null

    19

  0 files updated, 0 files merged, 1 files removed, 0 files unresolved

    20

  $ touch a

    21

different msg so we get a clog new entry

    22

  $ hg ci -Am b

    23

  adding a

    24

  created new head

    25

    26

pushing

    27

  $ hg push -f ../a

    28

  pushing to ../a

    29

  searching for changes

    30

  adding changesets

    31

  adding manifests

    32

  adding file changes

    33

  added 1 changesets with 0 changes to 0 files (+1 heads)

    34

    35

  $ cd ..