##// END OF EJS Templates
bisect: avoid adding irrelevant revisions to bisect state...
bisect: avoid adding irrelevant revisions to bisect state When adding new revisions to the bisect state, it only makes sense to add information about revisions that are under consideration (i.e., those that are topologically between the known good and bad revisions). However, if the user passes in a revset (e.g., '!merge()' to exclude merge commits), hg will resolve the revset first and add all matching revisions to the bisect state (which in this case would likely be the majority of revisions in the repo). To avoid this, revisions should only be added to the bisect state if they are between the good and bad revisions (and therefore relevant to the bisection). -- Here are the results of some performance tests using the `mozilla-central` repo (since it is one of the largest freely-available hg repositories in the wild). These tests compare the performance of a locally-built `hg` before and after application of this series. Note that `--noupdate` is passed to avoid including update time (which should not vary across cases). Setup (run between each test): $ hg bisect --reset $ hg bisect --noupdate --bad 56c3ad4bde5c70714b784ccf15d099e0df0f5bde $ hg bisect --noupdate --good 57426696adaf08298af3027fa77486fee0633b13 Test using a revset that returns a very large number of revisions: $ time hg bisect --noupdate --skip '!merge()' > /dev/null Before: real 0m9.398s user 0m9.233s sys 0m0.120s After: real 0m1.513s user 0m1.425s sys 0m0.052s Test using a revset that is expensive to compute: $ time hg bisect --noupdate --skip 'desc("Bug")' > /dev/null Before: real 0m49.853s user 0m49.580s sys 0m0.243s After: real 0m4.120s user 0m4.036s sys 0m0.048s

File last commit:

r48734:e5efbb11 default
r50337:81623652 default
Show More
test-bookmarks-corner-case.t
236 lines | 6.4 KiB | text/troff | Tads3Lexer
/ tests / test-bookmarks-corner-case.t
================================
Test corner case around bookmark
================================
This test file is meant to gather test around bookmark that are specific
enough to not find a place elsewhere.
Test bookmark/changelog race condition
======================================
The data from the bookmark file are filtered to only contains bookmark with
node known to the changelog. If the cache invalidation between these two bits
goes wrong, bookmark can be dropped.
Setup
-----
initial repository setup
$ hg init bookrace-server
$ cd bookrace-server
$ echo a > a
$ hg add a
$ hg commit -m root
$ echo a >> a
$ hg bookmark book-A
$ hg commit -m A0
$ hg up 'desc(root)'
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
(leaving bookmark book-A)
$ echo b > b
$ hg add b
$ hg bookmark book-B
$ hg commit -m B0
created new head
$ hg up null
0 files updated, 0 files merged, 2 files removed, 0 files unresolved
(leaving bookmark book-B)
$ hg phase --public --rev 'all()'
$ hg log -G
o changeset: 2:c79985706978
| bookmark: book-B
| tag: tip
| parent: 0:6569b5a81c7e
| user: test
| date: Thu Jan 01 00:00:00 1970 +0000
| summary: B0
|
| o changeset: 1:39c28d785860
|/ bookmark: book-A
| user: test
| date: Thu Jan 01 00:00:00 1970 +0000
| summary: A0
|
o changeset: 0:6569b5a81c7e
user: test
date: Thu Jan 01 00:00:00 1970 +0000
summary: root
$ hg book
book-A 1:39c28d785860
book-B 2:c79985706978
$ cd ..
Add new changeset on each bookmark in distinct clones
$ hg clone ssh://user@dummy/bookrace-server client-A
requesting all changes
adding changesets
adding manifests
adding file changes
added 3 changesets with 3 changes to 2 files (+1 heads)
new changesets 6569b5a81c7e:c79985706978
updating to branch default
2 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg -R client-A update book-A
1 files updated, 0 files merged, 1 files removed, 0 files unresolved
(activating bookmark book-A)
$ echo a >> client-A/a
$ hg -R client-A commit -m A1
$ hg clone ssh://user@dummy/bookrace-server client-B
requesting all changes
adding changesets
adding manifests
adding file changes
added 3 changesets with 3 changes to 2 files (+1 heads)
new changesets 6569b5a81c7e:c79985706978
updating to branch default
2 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg -R client-B update book-B
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
(activating bookmark book-B)
$ echo b >> client-B/b
$ hg -R client-B commit -m B1
extension to reproduce the race
-------------------------------
If two process are pushing we want to make sure the following happens:
* process A read changelog
* process B to its full push
* process A read bookmarks
* process A proceed with rest of the push
We build a server side extension for this purpose
$ cat > bookrace.py << EOF
> import atexit
> import os
> import time
> from mercurial import bookmarks, error, extensions
>
> def wait(repo):
> if not os.path.exists('push-A-started'):
> assert repo._currentlock(repo._lockref) is None
> assert repo._currentlock(repo._wlockref) is None
> repo.ui.status(b'setting raced push up\n')
> with open('push-A-started', 'w'):
> pass
> clock = 300
> while not os.path.exists('push-B-done'):
> clock -= 1
> if clock <= 0:
> raise error.Abort("race scenario timed out")
> time.sleep(0.1)
>
> def reposetup(ui, repo):
> class racedrepo(repo.__class__):
> @property
> def _bookmarks(self):
> wait(self)
> return super(racedrepo, self)._bookmarks
> repo.__class__ = racedrepo
>
> def e():
> with open('push-A-done', 'w'):
> pass
> atexit.register(e)
> EOF
Actual test
-----------
Start the raced push.
$ cat >> bookrace-server/.hg/hgrc << EOF
> [extensions]
> bookrace=$TESTTMP/bookrace.py
> EOF
$ hg push -R client-A -r book-A >push-output.txt 2>&1 &
Wait up to 30 seconds for that push to start.
$ clock=30
$ while [ ! -f push-A-started ] && [ $clock -gt 0 ] ; do
> clock=`expr $clock - 1`
> sleep 1
> done
Do the other push.
$ cat >> bookrace-server/.hg/hgrc << EOF
> [extensions]
> bookrace=!
> EOF
$ hg push -R client-B -r book-B
pushing to ssh://user@dummy/bookrace-server
searching for changes
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
updating bookmark book-B
Signal the raced put that we are done (it waits up to 30 seconds).
$ touch push-B-done
Wait for the raced push to finish (with the remaning of the initial 30 seconds).
$ while [ ! -f push-A-done ] && [ $clock -gt 0 ] ; do
> clock=`expr $clock - 1`
> sleep 1
> done
Check raced push output.
$ cat push-output.txt
pushing to ssh://user@dummy/bookrace-server
searching for changes
remote: setting raced push up
remote has heads on branch 'default' that are not known locally: f26c3b5167d1
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 1 changesets with 1 changes to 1 files
updating bookmark book-A
Check result of the push.
$ hg -R bookrace-server log -G
o changeset: 4:9ce3b28c16de
| bookmark: book-A
| tag: tip
| parent: 1:39c28d785860
| user: test
| date: Thu Jan 01 00:00:00 1970 +0000
| summary: A1
|
| o changeset: 3:f26c3b5167d1
| | bookmark: book-B
| | user: test
| | date: Thu Jan 01 00:00:00 1970 +0000
| | summary: B1
| |
| o changeset: 2:c79985706978
| | parent: 0:6569b5a81c7e
| | user: test
| | date: Thu Jan 01 00:00:00 1970 +0000
| | summary: B0
| |
o | changeset: 1:39c28d785860
|/ user: test
| date: Thu Jan 01 00:00:00 1970 +0000
| summary: A0
|
o changeset: 0:6569b5a81c7e
user: test
date: Thu Jan 01 00:00:00 1970 +0000
summary: root
$ hg -R bookrace-server book
book-A 4:9ce3b28c16de
book-B 3:f26c3b5167d1