- Oct 30, 2012
-
-
David M. Carr authored
This check is a remnant from back when we were using git-daemon in the tests.
-
durin42 authored
-
durin42 authored
-
David M. Carr authored
This isn't a real implementation of phases support. Rather, it's just enough to avoid the traceback. Traceback (most recent call last): File "/usr/local/share/python/hg", line 38, in <module> mercurial.dispatch.run() File "/usr/local/lib/python2.7/site-packages/mercurial/dispatch.py", line 28, in run sys.exit((dispatch(request(sys.argv[1:])) or 0) & 255) File "/usr/local/lib/python2.7/site-packages/mercurial/dispatch.py", line 65, in dispatch return _runcatch(req) File "/usr/local/lib/python2.7/site-packages/mercurial/dispatch.py", line 88, in _runcatch return _dispatch(req) File "/usr/local/lib/python2.7/site-packages/mercurial/dispatch.py", line 741, in _dispatch cmdpats, cmdoptions) File "/usr/local/lib/python2.7/site-packages/mercurial/dispatch.py", line 514, in runcommand ret = _runcommand(ui, options, cmd, d) File "/usr/local/lib/python2.7/site-packages/mercurial/dispatch.py", line 831, in _runcommand return checkargs() File "/usr/local/lib/python2.7/site-packages/mercurial/dispatch.py", line 802, in checkargs return cmdfunc() File "/usr/local/lib/python2.7/site-packages/mercurial/dispatch.py", line 738, in <lambda> d = lambda: util.checksignature(func)(ui, *args, **cmdoptions) File "/usr/local/lib/python2.7/site-packages/mercurial/util.py", line 472, in check return func(*args, **kwargs) File "/usr/local/lib/python2.7/site-packages/mercurial/commands.py", line 3942, in incoming return hg.incoming(ui, repo, source, opts) File "/usr/local/lib/python2.7/site-packages/mercurial/hg.py", line 525, in incoming return _incoming(display, subreporecurse, ui, repo, source, opts) File "/usr/local/lib/python2.7/site-packages/mercurial/hg.py", line 494, in _incoming displaychlist(other, chlist, displayer) File "/usr/local/lib/python2.7/site-packages/mercurial/hg.py", line 524, in display displayer.show(other[n]) File "/usr/local/lib/python2.7/site-packages/mercurial/cmdutil.py", line 670, in show self._show(ctx, copies, matchfn, props) File "/usr/local/lib/python2.7/site-packages/mercurial/cmdutil.py", line 691, in _show label='log.changeset changeset.%s' % ctx.phasestr()) File "/usr/local/lib/python2.7/site-packages/mercurial/context.py", line 203, in phasestr return phases.phasenames[self.phase()] File "/usr/local/lib/python2.7/site-packages/mercurial/context.py", line 201, in phase return self._repo._phasecache.phase(self._repo, self._rev) AttributeError: 'overlaychangectx' object has no attribute '_repo'
-
- Oct 29, 2012
-
-
David M. Carr authored
In converting this test to the unified format, it looks like we missed this line. It was accidentally being treated as a comment rather than executable.
-
David M. Carr authored
Now that hghave git works properly, uncomment the calls, and add ones that were missing.
-
David M. Carr authored
Previously, the hghave checks that were commented out in the tests were broken if uncommented. One cause was that it was expecting hghave in the testdir, while our testdir didn't contain hghave. Now it does. The hghave was pulled unmodified from Mercurial 2.3, to match the version of run-tests.py in use.
-
David M. Carr authored
Eliminate a find that would always return 0, based on an example in git_handler update_hg_bookmarks.
-
- Oct 27, 2012
-
-
David M. Carr authored
This should fix a bug introduced by 4f4ab2d89375 which caused all tags to be duplicated as bookmarks on pull. Test coverage has been added for pull to allow verifying the fix.
-
David M. Carr authored
This test wasn't actually testing anything to do with pulling.
-
- Oct 26, 2012
-
-
durin42 authored
-
David M. Carr authored
When communicating with the user on push/outgoing, Mercurial doesn't show a "exporting hg objects to git" message, so we shouldn't. The message has been changed to be shown if --verbose is specified.
-
David M. Carr authored
When communicating with the user on push, Mercurial doesn't show much on success. Currently, Hg-Git shows every changed ref. After this change, the default output will more closely match Mercurial's regular behavior (no per-ref output), while changed refs will be shown if --verbose is specified, and all refs will be shown if --debug is specified.
-
David M. Carr authored
-
David M. Carr authored
This changeset adds test coverage for comparing "hg outgoing -B" in normal Mercurial usage with Hg-Git usage. This didn't match, since previously, gitrepo didn't provide a meaningful listkeys implementation. Now, it does. gitrepo now has access to a GitHandler when a localrepo is available. This handler is used to access the information needed to implement listkeys for namespaces (currently, only bookmarks) and bookmarks. A couple of other tests were testing "divergent bookmark" scenarios. These tests have been updated to filter out the divergent bookmark output, as it isn't consistent across the supported Mercurial versions.
-
- Oct 25, 2012
-
-
David M. Carr authored
This change wraps hg.peer to allow for capturing the repo object. It is then passed in to new gitrepo instanceds. This will be needed to implement later functionality, such as richer bookmark support using pushkeys.
-
David M. Carr authored
In the logic that was attempting to handle the case where the local repo doesn't have any bookmarks, the assumption was being made that tip resolved to a non-null revision. In the case of a totally empty local repo, however, that isn't a valid assumption, and resulted in attempting to set the master ref to None, which broke dulwich. The "fix", which avoids the traceback and allows the push to complete (though still do nothing, since in this case there aren't any changes to push), is to not tweak the refs at all if tip is nullid. Leaving the special capabilities ref and not adding a master ref appears to be fine in this case.
-
- Oct 18, 2012
-
-
Jordi Gutiérrez Hermoso authored
Python 2.4 does not have a with-statement
-
- Oct 17, 2012
- Oct 08, 2012
-
-
David M. Carr authored
test-bookmark-workflow.t now skips all Mercurial versions below 2.1, as the return code is different, and it's more important for this test to accurately show that we match the behavior of current Mercurial than that all versions behave the same.
-
David M. Carr authored
The output for "hg push" when there were no changes didn't quite match between Mercurial with and without Hg-Git, so I changed the behavior to bring it into synch. The existing "creating and sending data" message was changed to be included if --verbose is specified.
-
- Oct 07, 2012
-
-
David M. Carr authored
-
David M. Carr authored
-
David M. Carr authored
I was seeing sporadic failures running this test on Mac OS X 10.8. They looked like this: + sed: 1: "s_/private/var/folders/ ...": bad flag in substitute command: 'T' My assumption is that some character was being included in the path of the temporary directory that sed didn't like. It looks like the sed function was being used to eliminate differences between test runs due to the path changing each run. That isn't needed any more now that we're using the unified test format, since said replacement is taken care of for us by run-tests.py. Thus, this changeset removes the calls to sed and updates the output to use the result from the framework-level replacement.
-
- Sep 28, 2012
-
-
David M. Carr authored
Mercurial has support for including information about the tested versions of Mercurial for an extension when it detects that an extension has broken. This change includes the appropriate attribute in the extension.
-
David M. Carr authored
Mercurial has support for including a link to an issue tracker when it detects that an extension has broken. This change includes the appropriate attribute in the extension, pointing it at the issue tracker for the main BitBucket repo.
-
David M. Carr authored
There was a bug introduced in 8c1f2b07c04b such that calling hg outgoing on a Git repository would result in all refs being deleted from the remote repository (with the possible exception of the currently checked out branch). It wasn't noticed before because the existing test for outgoing didn't actually verify the refs on the remote. This changeset fixes the bug, as well as adding test coverage to allow verifying that the fix works.
-
- Sep 22, 2012
-
-
Gregory Szorc authored
When exporting Git commits, verify that the tree and parents objects exist in the repository before allowing the commit to be exported. If a tree or parent commit is missing, then the repository is not valid and the export should not be allowed.
-
Gregory Szorc authored
-
Gregory Szorc authored
-
Gregory Szorc authored
-
Gregory Szorc authored
-
Gregory Szorc authored
-
Gregory Szorc authored
Pre-compile regular expression. Prevent extra key lookup in author_map.
-
- Sep 16, 2012
-
-
Sean Farley authored
-
- Sep 14, 2012
-
-
David M. Carr authored
This change was already applied to all the other tests.
-
David M. Carr authored
This change was already applied to all the other tests.
-
David M. Carr authored
This change was already applied to all the other tests.
-
David M. Carr authored
-