##// END OF EJS Templates
streamclone: disable the volatile file open handle optimization on Windows...
streamclone: disable the volatile file open handle optimization on Windows Leaving files open caused new failures like this, since a47f09da8bd1: diff --git a/tests/test-persistent-nodemap-stream-clone.t b/tests/test-persistent-nodemap-stream-clone.t --- a/tests/test-persistent-nodemap-stream-clone.t +++ b/tests/test-persistent-nodemap-stream-clone.t @@ -115,7 +115,12 @@ Do a mix of clone and commit at the same $ (hg clone -U --stream ssh://user@dummy/test-repo stream-clone-race-1 --debug 2>> clone-output | grep -E '00(changelog|manifest)' >> clone-output; touch $HG_TEST_STREAM_WALKED_FILE_3) & $ $RUNTESTDIR/testlib/wait-on-file 10 $HG_TEST_STREAM_WALKED_FILE_1 $ hg -R test-repo/ commit -m foo - created new head + transaction abort! + failed to recover 00changelog.n ([WinError 32] The process cannot access the file because it is being used by another process: b'$STR_REPR_TESTTMP\\test-repo/.hg/store/00changelog.n' -> b'$STR_REPR_TESTTMP\\test-repo/.hg/store/00changelog.n-f418dcd6') + rollback failed - please run hg recover + (failure reason: [WinError 32] The process cannot access the file because it is being used by another process: b'$STR_REPR_TESTTMP\\test-repo/.hg/store/00changelog.n' -> b'$STR_REPR_TESTTMP\\test-repo/.hg/store/00changelog.n-f418dcd6') + abort: The process cannot access the file because it is being used by another process: '$TESTTMP\test-repo\.hg\store\00changelog.n' + [255] $ touch $HG_TEST_STREAM_WALKED_FILE_2 $ $RUNTESTDIR/testlib/wait-on-file 10 $HG_TEST_STREAM_WALKED_FILE_3 $ cat clone-output Since the `VolatileManager` falls back to the old copy method when the open file threshold is exceeded, this just drops the threshold so that only 1 file is open. The actual value used (2) is unexpected, and explained inline. I'd like to have a config option for this so that we can test both ways (in theory, it could resort to copies on non-Windows systems too), but I don't see a `uimod.ui` handy. Alternately, I tried replacing the 3 `open()` calls in the `VolatileManager` with `util.posixfile()`, but that simply hung the test on Windows for some reason, I think on the same line that's indicated as failing above. (There was a `grep` command hanging around, as well as `hg -R test-repo serve --stdio`.)
Matt Harbison -
r53081:e4b242f9 stable
Show More
Name Size Modified Last Commit Author
/ contrib / win32
ReadMe.html Loading ...
buildlocal.bat Loading ...
hg.bat Loading ...
hgwebdir_wsgi.py Loading ...
mercurial.ico Loading ...
mercurial.ini Loading ...
postinstall.txt Loading ...


<html>
<head>
<title>Mercurial for Windows</title>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" >
<style type="text/css">

</style>
</head>

<body>

Mercurial for Windows



Welcome to Mercurial for Windows!




Mercurial is a command-line application. You must run it from
the Windows command prompt (or if you're hard core, a <a<br /> href="http://www.mingw.org/">MinGW shell).




Note: the standard http://www.mingw.org/">MinGW
msys startup script uses rxvt which has problems setting up
standard input and output. Running bash directly works
correctly.




For documentation, please visit the <a<br /> href="https://mercurial-scm.org/">Mercurial web site.
You can also download a free book, <a<br /> href="https://book.mercurial-scm.org/">Mercurial: The Definitive
Guide.




By default, Mercurial installs to C:\Program
Files\Mercurial
. The Mercurial command is called
hg.exe.



Testing Mercurial after you've installed it




The easiest way to check that Mercurial is installed properly is
to just type the following at the command prompt:




hg



This command should print a useful help message. If it does,
other Mercurial commands should work fine for you.



Configuration notes


Default editor



The default editor for commit messages is 'notepad'. You can set
the EDITOR (or HGEDITOR) environment variable
to specify your preference or set it in mercurial.ini:



[ui]
editor = whatever


Configuring a Merge program



It should be emphasized that Mercurial by itself doesn't attempt
to do a Merge at the file level, neither does it make any
attempt to Resolve the conflicts.




By default, Mercurial will use the merge program defined by the
HGMERGE environment variable, or uses the one defined
in the mercurial.ini file. (see <a<br /> href="https://mercurial-scm.org/wiki/MergeProgram">MergeProgram
on the Mercurial Wiki for more information)



Reporting problems




Before you report any problems, please consult the <a<br /> href="https://mercurial-scm.org/">Mercurial web site
and see if your question is already in our list of <a<br /> href="https://mercurial-scm.org/wiki/FAQ">Frequently
Answered Questions (the "FAQ").




If you cannot find an answer to your question, please feel free
to send mail to the Mercurial mailing list, at <a<br /> href="mailto:mercurial@mercurial-scm.org">mercurial@mercurial-scm.org.
Remember, the more useful information you include in your
report, the easier it will be for us to help you!




If you are IRC-savvy, that's usually the fastest way to get
help. Go to #mercurial on irc.freenode.net.



Author and copyright information




Mercurial was written by http://www.selenic.com">Matt
Mackall, and is maintained by Matt and a team of volunteers.




The Windows installer was written by <a<br /> href="http://www.serpentine.com/blog">Bryan O'Sullivan.




Mercurial is Copyright 2005-2024 Olivia Mackall and others.




Mercurial is free software; you can redistribute it and/or
modify it under the terms of the <a<br /> href="http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt">GNU
General Public License version 2 or any later version.




Mercurial is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty
of merchantability or fitness for a particular
purpose
. See the GNU General Public License for more
details.


</body>
</html>