2019-12-10 02:24:31 +03:00
|
|
|
#chg-compatible
|
|
|
|
|
2018-06-26 05:34:37 +03:00
|
|
|
Race detector will complain about this test.
|
|
|
|
|
|
|
|
$ setconfig fsmonitor.detectrace=0
|
|
|
|
|
2017-06-03 08:27:52 +03:00
|
|
|
$ hg init repo
|
|
|
|
$ cd repo
|
2010-09-14 14:20:51 +04:00
|
|
|
$ echo a > a
|
|
|
|
$ hg add a
|
|
|
|
$ hg commit -m test
|
|
|
|
|
|
|
|
Do we ever miss a sub-second change?:
|
|
|
|
|
|
|
|
$ for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20; do
|
|
|
|
> hg co -qC 0
|
|
|
|
> echo b > a
|
|
|
|
> hg st
|
|
|
|
> done
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
M a
|
|
|
|
|
2017-06-03 08:27:52 +03:00
|
|
|
$ echo test > b
|
|
|
|
$ mkdir dir1
|
|
|
|
$ echo test > dir1/c
|
|
|
|
$ echo test > d
|
|
|
|
|
|
|
|
$ echo test > e
|
|
|
|
#if execbit
|
|
|
|
A directory will typically have the execute bit -- make sure it doesn't get
|
|
|
|
confused with a file with the exec bit set
|
|
|
|
$ chmod +x e
|
|
|
|
#endif
|
|
|
|
|
|
|
|
$ hg add b dir1 d e
|
2017-12-11 06:50:57 +03:00
|
|
|
adding dir1/c
|
2017-06-03 08:27:52 +03:00
|
|
|
$ hg commit -m test2
|
|
|
|
|
|
|
|
$ cat >> $TESTTMP/dirstaterace.py << EOF
|
2019-01-30 03:25:33 +03:00
|
|
|
> from edenscm.mercurial import (
|
2017-06-03 08:27:52 +03:00
|
|
|
> extensions,
|
2020-01-15 04:45:49 +03:00
|
|
|
> filesystem,
|
2017-06-03 08:27:52 +03:00
|
|
|
> )
|
2020-01-15 04:45:49 +03:00
|
|
|
> from edenscm.hgext import fsmonitor
|
2017-06-03 08:27:52 +03:00
|
|
|
> def extsetup():
|
2020-01-15 04:45:49 +03:00
|
|
|
> extensions.wrapfunction(filesystem.physicalfilesystem, '_postpendingfixup', overridepostpending)
|
2020-01-15 04:45:49 +03:00
|
|
|
> extensions.wrapfunction(fsmonitor.fsmonitorfilesystem, '_fspostpendingfixup', overridepostpending)
|
|
|
|
> def overridepostpending(orig, self, *args):
|
2017-06-03 08:27:52 +03:00
|
|
|
> # make an update that changes the dirstate from underneath
|
2020-01-15 04:45:49 +03:00
|
|
|
> self.dirstate._repo.ui.system(r"sh '$TESTTMP/dirstaterace.sh'",
|
|
|
|
> cwd=self.dirstate._repo.root)
|
2020-01-15 04:45:49 +03:00
|
|
|
> return orig(self, *args)
|
2017-06-03 08:27:52 +03:00
|
|
|
> EOF
|
|
|
|
|
|
|
|
$ hg debugrebuilddirstate
|
|
|
|
$ hg debugdirstate
|
|
|
|
n 0 -1 unset a
|
|
|
|
n 0 -1 unset b
|
|
|
|
n 0 -1 unset d
|
|
|
|
n 0 -1 unset dir1/c
|
|
|
|
n 0 -1 unset e
|
|
|
|
|
2020-01-15 04:45:49 +03:00
|
|
|
Test deleting some files after lookup but before being marked clean. Verify
|
|
|
|
they remain lookup/unset afterwards.
|
2017-06-03 08:27:52 +03:00
|
|
|
|
2017-06-09 07:07:49 +03:00
|
|
|
$ cat > $TESTTMP/dirstaterace.sh <<EOF
|
|
|
|
> rm b && rm -r dir1 && rm d && mkdir d && rm e && mkdir e
|
|
|
|
> EOF
|
|
|
|
|
2020-01-15 04:45:49 +03:00
|
|
|
$ hg status --traceback --config extensions.dirstaterace=$TESTTMP/dirstaterace.py
|
|
|
|
$ hg status
|
2017-06-03 08:27:52 +03:00
|
|
|
! b
|
2020-01-15 04:45:49 +03:00
|
|
|
! d
|
2017-06-03 08:27:52 +03:00
|
|
|
! dir1/c
|
2020-01-15 04:45:49 +03:00
|
|
|
! e
|
|
|
|
|
2017-06-03 08:27:52 +03:00
|
|
|
$ hg debugdirstate
|
|
|
|
n 644 2 * a (glob)
|
|
|
|
n 0 -1 unset b
|
|
|
|
n 0 -1 unset d
|
|
|
|
n 0 -1 unset dir1/c
|
|
|
|
n 0 -1 unset e
|
|
|
|
|
|
|
|
$ hg status
|
|
|
|
! b
|
|
|
|
! d
|
|
|
|
! dir1/c
|
|
|
|
! e
|
2017-06-09 07:07:49 +03:00
|
|
|
|
|
|
|
$ rmdir d e
|
|
|
|
$ hg update -C -q .
|
|
|
|
|
|
|
|
Test that dirstate changes aren't written out at the end of "hg
|
|
|
|
status", if .hg/dirstate is already changed simultaneously before
|
2017-06-12 23:54:59 +03:00
|
|
|
acquisition of wlock in workingctx._poststatusfixup().
|
2017-06-09 07:07:49 +03:00
|
|
|
|
|
|
|
This avoidance is important to keep consistency of dirstate in race
|
|
|
|
condition (see issue5584 for detail).
|
|
|
|
|
|
|
|
$ hg parents -q
|
2020-07-21 03:23:52 +03:00
|
|
|
* (glob)
|
2017-06-09 07:07:49 +03:00
|
|
|
|
|
|
|
$ hg debugrebuilddirstate
|
|
|
|
$ hg debugdirstate
|
|
|
|
n 0 -1 unset a
|
|
|
|
n 0 -1 unset b
|
|
|
|
n 0 -1 unset d
|
|
|
|
n 0 -1 unset dir1/c
|
|
|
|
n 0 -1 unset e
|
|
|
|
|
|
|
|
$ cat > $TESTTMP/dirstaterace.sh <<EOF
|
|
|
|
> # This script assumes timetable of typical issue5584 case below:
|
|
|
|
> #
|
|
|
|
> # 1. "hg status" loads .hg/dirstate
|
|
|
|
> # 2. "hg status" confirms clean-ness of FILE
|
|
|
|
> # 3. "hg update -C 0" updates the working directory simultaneously
|
|
|
|
> # (FILE is removed, and FILE is dropped from .hg/dirstate)
|
|
|
|
> # 4. "hg status" acquires wlock
|
|
|
|
> # (.hg/dirstate is re-loaded = no FILE entry in dirstate)
|
|
|
|
> # 5. "hg status" marks FILE in dirstate as clean
|
|
|
|
> # (FILE entry is added to in-memory dirstate)
|
|
|
|
> # 6. "hg status" writes dirstate changes into .hg/dirstate
|
|
|
|
> # (FILE entry is written into .hg/dirstate)
|
|
|
|
> #
|
|
|
|
> # To reproduce similar situation easily and certainly, #2 and #3
|
|
|
|
> # are swapped. "hg cat" below ensures #2 on "hg status" side.
|
|
|
|
>
|
|
|
|
> hg update -q -C 0
|
|
|
|
> hg cat -r 1 b > b
|
|
|
|
> EOF
|
|
|
|
|
|
|
|
"hg status" below should excludes "e", of which exec flag is set, for
|
|
|
|
portability of test scenario, because unsure but missing "e" is
|
|
|
|
treated differently in _checklookup() according to runtime platform.
|
|
|
|
|
|
|
|
- "missing(!)" on POSIX, "pctx[f].cmp(self[f])" raises ENOENT
|
|
|
|
- "modified(M)" on Windows, "self.flags(f) != pctx.flags(f)" is True
|
|
|
|
|
context: wait for wlock for dirstate fixup if watchman reports fresh instance
Summary:
This is an attempt to solve issues that watchman state in dirstate stays stale
and users have pretty bad experience.
Normally, `hg status` is a "read-only" operation that works in a lock-free way,
and `status` still work if other hg commands are taking a lock. However,
`hg status` does need to update watchman state (clock, need-check file list) to
stay performant.
In case watchman reports "fresh instance" case, watchman also returns all file
paths in the working copy, which means the current `status` has very bad
performance, and the next `status` call can still be bad if the watchman state
in dirstate does not get updated.
This diff adds special handling of "fresh instance", waits for the lock, and
attempts to update the watchman state. It should reduce user frustration about
continuously slow `hg status` commands. In case it failed to update the
watchman state, also print warning messages so the user is aware of the issue.
For example, if there is an ongoing `hg histedit` that waits for the editor.
Reviewed By: wez
Differential Revision: D17468790
fbshipit-source-id: ad06bb1d5d13c6904db328c42a470112c3ee9940
2019-09-20 05:06:16 +03:00
|
|
|
#if fsmonitor
|
2017-06-09 07:07:49 +03:00
|
|
|
$ hg status --config extensions.dirstaterace=$TESTTMP/dirstaterace.py --debug -X path:e
|
2020-01-15 04:45:49 +03:00
|
|
|
skip updating dirstate: identity mismatch
|
context: wait for wlock for dirstate fixup if watchman reports fresh instance
Summary:
This is an attempt to solve issues that watchman state in dirstate stays stale
and users have pretty bad experience.
Normally, `hg status` is a "read-only" operation that works in a lock-free way,
and `status` still work if other hg commands are taking a lock. However,
`hg status` does need to update watchman state (clock, need-check file list) to
stay performant.
In case watchman reports "fresh instance" case, watchman also returns all file
paths in the working copy, which means the current `status` has very bad
performance, and the next `status` call can still be bad if the watchman state
in dirstate does not get updated.
This diff adds special handling of "fresh instance", waits for the lock, and
attempts to update the watchman state. It should reduce user frustration about
continuously slow `hg status` commands. In case it failed to update the
watchman state, also print warning messages so the user is aware of the issue.
For example, if there is an ongoing `hg histedit` that waits for the editor.
Reviewed By: wez
Differential Revision: D17468790
fbshipit-source-id: ad06bb1d5d13c6904db328c42a470112c3ee9940
2019-09-20 05:06:16 +03:00
|
|
|
#else
|
|
|
|
$ hg status --config extensions.dirstaterace=$TESTTMP/dirstaterace.py --debug -X path:e
|
2020-01-15 04:45:49 +03:00
|
|
|
skip marking lookups clean: identity mismatch
|
context: wait for wlock for dirstate fixup if watchman reports fresh instance
Summary:
This is an attempt to solve issues that watchman state in dirstate stays stale
and users have pretty bad experience.
Normally, `hg status` is a "read-only" operation that works in a lock-free way,
and `status` still work if other hg commands are taking a lock. However,
`hg status` does need to update watchman state (clock, need-check file list) to
stay performant.
In case watchman reports "fresh instance" case, watchman also returns all file
paths in the working copy, which means the current `status` has very bad
performance, and the next `status` call can still be bad if the watchman state
in dirstate does not get updated.
This diff adds special handling of "fresh instance", waits for the lock, and
attempts to update the watchman state. It should reduce user frustration about
continuously slow `hg status` commands. In case it failed to update the
watchman state, also print warning messages so the user is aware of the issue.
For example, if there is an ongoing `hg histedit` that waits for the editor.
Reviewed By: wez
Differential Revision: D17468790
fbshipit-source-id: ad06bb1d5d13c6904db328c42a470112c3ee9940
2019-09-20 05:06:16 +03:00
|
|
|
#endif
|
2017-06-09 07:07:49 +03:00
|
|
|
|
2020-01-15 04:45:49 +03:00
|
|
|
$ hg status --debug -X path:e
|
|
|
|
? b
|
|
|
|
|
2017-06-09 07:07:49 +03:00
|
|
|
$ hg parents -q
|
2020-07-21 03:23:52 +03:00
|
|
|
* (glob)
|
2017-06-09 07:07:49 +03:00
|
|
|
$ hg files
|
|
|
|
a
|
|
|
|
$ hg debugdirstate
|
2017-06-12 23:10:09 +03:00
|
|
|
n * * * a (glob)
|
2017-06-13 01:34:31 +03:00
|
|
|
|
|
|
|
$ rm b
|
|
|
|
|
|
|
|
Set up a rebase situation for issue5581.
|
|
|
|
|
|
|
|
$ echo c2 > a
|
|
|
|
$ echo c2 > b
|
|
|
|
$ hg add b
|
|
|
|
$ hg commit -m c2
|
|
|
|
$ echo c3 >> a
|
|
|
|
$ hg commit -m c3
|
2020-10-08 21:06:31 +03:00
|
|
|
$ hg update 'desc(c2)'
|
2017-06-13 01:34:31 +03:00
|
|
|
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
|
|
|
|
$ echo c4 >> a
|
|
|
|
$ echo c4 >> b
|
|
|
|
$ hg commit -m c4
|
|
|
|
|
2017-07-21 04:04:21 +03:00
|
|
|
Configure a merge tool that runs status in the middle of the rebase. The goal of
|
|
|
|
the status call is to trigger a potential bug if fsmonitor's state is written
|
|
|
|
even though the wlock is held by another process. The output of 'hg status' in
|
|
|
|
the merge tool goes to /dev/null because we're more interested in the results of
|
|
|
|
'hg status' run after the rebase.
|
2017-06-13 01:34:31 +03:00
|
|
|
|
|
|
|
$ cat >> $TESTTMP/mergetool-race.sh << EOF
|
|
|
|
> echo "custom merge tool"
|
|
|
|
> printf "c2\nc3\nc4\n" > \$1
|
2018-06-20 20:55:23 +03:00
|
|
|
> hg --cwd "$TESTTMP/repo" status --pager=off > /dev/null
|
2017-06-13 01:34:31 +03:00
|
|
|
> echo "custom merge tool end"
|
|
|
|
> EOF
|
|
|
|
$ cat >> $HGRCPATH << EOF
|
|
|
|
> [extensions]
|
|
|
|
> rebase =
|
|
|
|
> [merge-tools]
|
|
|
|
> test.executable=sh
|
|
|
|
> test.args=$TESTTMP/mergetool-race.sh \$output
|
|
|
|
> EOF
|
|
|
|
|
2020-10-08 21:06:31 +03:00
|
|
|
$ hg rebase -s . -d 'desc(c3)' --tool test
|
2019-12-18 00:45:17 +03:00
|
|
|
rebasing b08445fd6b2a "c4"
|
2017-06-13 01:34:31 +03:00
|
|
|
merging a
|
|
|
|
custom merge tool
|
|
|
|
custom merge tool end
|
|
|
|
|
|
|
|
This hg status should be empty, whether or not fsmonitor is enabled (issue5581).
|
|
|
|
|
|
|
|
$ hg status
|