[Bug 5588] New: fsmonitor fails with "watchman command error: unable to resolve root" on Windows MSYS environment

mercurial-bugs at mercurial-scm.org mercurial-bugs at mercurial-scm.org
Tue Jun 6 11:57:18 EDT 2017


            Bug ID: 5588
           Summary: fsmonitor fails with "watchman command error: unable
                    to resolve root" on Windows MSYS environment
           Product: Mercurial
           Version: 4.2.1
          Hardware: PC
                OS: Windows
            Status: UNCONFIRMED
          Severity: feature
          Priority: wish
         Component: fsmonitor
          Assignee: bugzilla at mercurial-scm.org
          Reporter: rvandermeulen at mozilla.com
                CC: gregory.szorc at gmail.com,
                    mercurial-devel at mercurial-scm.org

Hi, I maintain the MozillaBuild package that Mozilla distributes to provide a
build toolchain on Windows.

Our basic setup is as follows:
* MSYS toolchain (the original, not msys2)
* Python for Windows (version 2.7.13)
* Mercurial installed via pip (version 4.2.1)

I've recently been trying to test the native fsmonitor with the latest watchman
binary from upstream (rev 98b6d81 downloaded from the appveyor CI artifacts).
With watchman added to my path, I've confirmed that I can properly invoke it
from the command prompt:

$ watchman -v

However, when I set fsmonitor.mode = on, I get the following error whenever I
perform any operations:
warning: Watchman unavailable: watchman command error: unable to resolve root
c:\Users\Ryan\repos\mozilla-build: "c:\Users\Ryan\repos\mozilla-build" resolved
to "C:/Users/Ryan/repos/mozilla-build" but we were unable to examine
"c:\Users\Ryan\repos\mozilla-build" using strict case sensitive rules.  Please
check each component of the path and make sure that that path exactly matches
the correct case of the files on your filesystem.

I've also checked and confirmed that the value of ui.slash has no bearing on
whether this error hits or not. I'd previously been able to use hgwatchman
(along with an older build of watchman) in this configuration, not entirely
bug-free, but it worked anyway, so this appears to be a regression somewhere
along the way.

If you'd like to download a test package the replicates the environment above,
it is available from the link below:

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

More information about the Mercurial-devel mailing list