tests on windows

Patrick Mézard pmezard at gmail.com
Mon Jan 21 03:38:16 CST 2008


j w a écrit :
> I'm trying to get Mercurial's tests running on Windows.
> I'm using the instructions here:
> http://www.selenic.com/mercurial/wiki/index.cgi/WindowsTestingPlan
> but when I get to step 3 - "Clone the related patch queue...", I am
> having issues.
> 
> Maybe because I have not used cloned patch queues before (:
> Inside my cloned crew directory, I tried running this:
> 
> hg qclone http://hg.intevation.org/beta/mercurial/pmezard/crew-stable-w32.mq/
>  requesting all changes
>  adding changesets
>  adding manifests
>  adding file changes
>  added 13 changesets with 129 changes to 74 files
>  abort: HTTP Error 404: Not Found

qclone is used to clone a repository and its related patch queue repository. Here, crew-stable-w32.mq is a standalone patch queue repository, so you would just use "hg clone http://hg.intevation.org/beta/mercurial/pmezard/crew-stable-w32.mq/" and put it in you crew-stable clone as .hg/patches (to use it as a normal patch queue).

Then just:

$ hg qpush -a

All patches should apply clean (I say should because I am lagging a little these days to update the patch queues, but crew-stable is stable enough that it should not matter). If it does not, move in .hg/patches and "hg tip". The changelog message lists the last mercurial revision the patch queue was applied on. At least you will have a working setup.

As you guessed, the "use_pysh" patch modifies run-tests.py to run shell scripts under windows.

Also, testhg.py is no longer used (and was removed from pysh). I will update the wiki ASAP.

Thank you for trying this, please keep posting about other issues you may have.

--
Patrick Mézard


More information about the Mercurial-devel mailing list