sapling/eden/scm/tests/test-hggit-timezone.t
Zeyi (Rice) Fan 92f6f35e7a mark all tests requiring Python 2
Summary:
This diff marks **ALL** mercurial tests requiring Python 2 feature.

After you fixes some tests, simply remove the `py2` feature requirement and that tests will be continuously run after your diff is landed.

To bypass this feature requirement, run the tests command with `HGTEST_FORCE_PY2=1`. For example:

```
HGTEST_FORCE_PY2=1 buck test //eden/scm/tests:hg_run_tests
```

or

```
HGTEST_FORCE_PY2=1 python run-tests.py
```

----

Basically this diff are created with the following commands:

```
$ sed -i 's/import feature\(.*\)$/import feature\1\n\nfeature.require(["py2"])/' test-*-t.py
$ sed -i '1s/^/#require py2\n/' test-*.t
$ ls | grep -P "^test.*(?<\!-t)\.py$" > list && vim -p $(cat list)
# manually adding feature requires for these Python tests.
```

(Note: this ignores all push blocking failures!)

ignore-conflict-markers

Reviewed By: singhsrb

Differential Revision: D19655148

fbshipit-source-id: 985e3ccb4010cc559049f1d89f8909bc2d9b5e20
2020-01-30 18:49:21 -08:00

34 lines
870 B
Perl

#require py2
This test shows how dulwich fails to convert a commit accepted by hg.
In the real world case, it was a hand edit by the user to change the
timezone field in an export. However, if it is good enough for hg, we
have to make it good enough for git.
Load commonly used test logic
$ . "$TESTDIR/hggit/testutil"
$ hg init hgrepo
$ cd hgrepo
$ touch beta
$ hg add beta
$ fn_hg_commit -m "test commit"
$ cat >patch2 <<EOF
> # HG changeset patch
> # User J. User <juser@example.com>
> # Date 1337962044 25201
> # Node ID 1111111111111111111111111111111111111111
> # Parent 0000000000000000000000000000000000000000
>
> Patch with sub-minute time zone
> diff --git a/alpha b/alpha
> new file mode 100644
> --- /dev/null
> +++ b/alpha
> @@ -0,0 +1,1 @@
> +alpha
> EOF
$ hg import patch2
applying patch2
$ hg gexport