Mercurial > hg
view tests/test-issue1102.t @ 49991:3997c64eff8b
test: use a more direct approach to test racy mutation
The previous test was relying on implementation details and harder to maintain.
The new version is closer to the initial intend : "What happens the file get overwritten from under the current process"
This change is motivated by further changes around the transaction and dirstate
logic that would break the fragile equilibrium that existed before this patch.
Making this change early make it easier to review on its own and remove noise
in future larger changes.
author | Pierre-Yves David <pierre-yves.david@octobus.net> |
---|---|
date | Tue, 07 Feb 2023 13:14:59 +0100 |
parents | 805419729e11 |
children |
line wrap: on
line source
$ rm -rf a $ hg init a $ cd a $ echo a > a $ hg ci -Am0 adding a $ hg tag t1 # 1 $ hg tag --remove t1 # 2 $ hg co 1 1 files updated, 0 files merged, 0 files removed, 0 files unresolved $ hg tag -f -r0 t1 $ hg tags tip 3:a49829c4fc11 t1 0:f7b1eb17ad24 Ensure that the username access fails gracefully if assumptions about the environment made by python do not hold. #if windows >>> import os >>> from mercurial import util >>> os.environ.pop('LOGNAME', None) and None >>> os.environ.pop('USER', None) and None >>> os.environ.pop('LNAME', None) and None >>> os.environ.pop('USERNAME', None) and None >>> print(util.username()) None #endif $ cd ..