Mercurial > hg
comparison tests/test-dirstate-race.t @ 48389:03644a929d6e
test: use a different timestamp for the updated file
In the test we want to trigger a write after the underlying dirstate changed. To
do so, we need a write. And as we are about to make dirstate update smarter we
need to meddle with the script a bit to make sure there will be a write.
Differential Revision: https://phab.mercurial-scm.org/D11793
author | Pierre-Yves David <pierre-yves.david@octobus.net> |
---|---|
date | Thu, 18 Nov 2021 15:00:13 +0100 |
parents | 4c61c7f75de6 |
children | 322525db4c98 |
comparison
equal
deleted
inserted
replaced
48388:f5dea753fe4e | 48389:03644a929d6e |
---|---|
146 > # To reproduce similar situation easily and certainly, #2 and #3 | 146 > # To reproduce similar situation easily and certainly, #2 and #3 |
147 > # are swapped. "hg cat" below ensures #2 on "hg status" side. | 147 > # are swapped. "hg cat" below ensures #2 on "hg status" side. |
148 > | 148 > |
149 > hg update -q -C 0 | 149 > hg update -q -C 0 |
150 > hg cat -r 1 b > b | 150 > hg cat -r 1 b > b |
151 > # make sure the timestamps is not ambiguous and a write will be issued | |
152 > touch -t 198606251012 b | |
151 > EOF | 153 > EOF |
152 | 154 |
153 "hg status" below should excludes "e", of which exec flag is set, for | 155 "hg status" below should excludes "e", of which exec flag is set, for |
154 portability of test scenario, because unsure but missing "e" is | 156 portability of test scenario, because unsure but missing "e" is |
155 treated differently in _checklookup() according to runtime platform. | 157 treated differently in _checklookup() according to runtime platform. |