-
Bug
-
Resolution: Unresolved
-
Minor
-
Windows Server 2008R2, TortoiseHg
When the Mercurial polling fails because the repository is not in the given location, it prints an error but then continues without raising any other visible alert. I only happened to see that it said aborted in the middle of the log message. See attached screenshot (confidential names erased).
Ideas for correction:
- Fail the entire polling (stop execution)
- Log the error centrally in the system log so it more easily can be detected