[Bug 6696] New: test-dirstate.t#dirstate-v2 failing with Rust detection

[mercurial-bugs at mercurial-scm.org]

https://bz.mercurial-scm.org/show_bug.cgi?id=6696

            Bug ID: 6696
           Summary: test-dirstate.t#dirstate-v2 failing with Rust
                    detection
           Product: Mercurial
           Version: 6.1.2
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: bug
          Priority: wish
         Component: Mercurial
          Assignee: bugzilla at mercurial-scm.org
          Reporter: kwalkq.mercurial-bugzilla at pacien.net
                CC: mercurial-devel at mercurial-scm.org
    Python Version: ---

test-dirstate.t#dirstate-v2 fails on 6.1.2 on NixOS.
This test was passing fine on 6.1.1 in the same environment.

The build has the Rust-related options enabled.

This problem could have been introduced with 682b0ac92c0b or 5d610521a285,
which seem related to Rust detection in tests.

```diff
--- /build/mercurial-6.1.2/tests/test-dirstate.t
+++ /build/mercurial-6.1.2/tests/test-dirstate.t#dirstate-v2.err
@@ -159,6 +159,7 @@
    *1 (re)
   $ dirstate_uuid_has_not_changed
   not testing because using Python implementation (no-rust no-rhg !)
+  not testing because using Python implementation
 Trigger an append with a small change
@@ -169,6 +170,7 @@
    *1 (re)
   $ dirstate_uuid_has_not_changed
   not testing because using Python implementation (no-rust no-rhg !)
+  not testing because using Python implementation
 Unused bytes counter is non-0 when appending
   $ touch file
@@ -183,6 +185,7 @@
    *1 (re)
   $ dirstate_uuid_has_not_changed
   not testing because using Python implementation (no-rust no-rhg !)
+  not testing because using Python implementation
   $ hg debugstate --docket | grep unused
   number of unused bytes: 0 (no-rust no-rhg !)
ERROR: test-dirstate.t#dirstate-v2 output changed
```

Full build and test log:
https://logs.nix.ci/?key=nixos/nixpkgs.171565&attempt_id=463df95b-f00b-43af-a5cb-b905536c99b6

-- 
You are receiving this mail because:
You are on the CC list for the bug.