Can anyone point me in right direction for this error?

Issue #5074 invalid
jstrong611
created an issue

Here is an error report I am receiving in Eclipse when I attempt a Merge:

eclipse.buildId=4.7.3.M20180330-0640
java.version=1.8.0_171
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product -product org.eclipse.epp.package.jee.product -data file:/C:/Users/John/Documents/Workspace-BoC/ -product org.eclipse.epp.package.jee.product

com.vectrace.MercurialEclipse
Error
Mon Apr 23 12:44:23 EDT 2018
Unexpected format: updated to "d9f4a675b793: Merge Test"

com.aragost.javahg.internals.UnexpectedCommandOutputException: Unexpected format: updated to "d9f4a675b793: Merge Test"
    at com.aragost.javahg.commands.UpdateResult.fromLine(UpdateResult.java:123)
    at com.aragost.javahg.internals.UpdateMergeHelper.update(UpdateMergeHelper.java:95)
    at com.aragost.javahg.commands.UpdateCommand.executeHelper(UpdateCommand.java:80)
    at com.aragost.javahg.commands.UpdateCommand.execute(UpdateCommand.java:58)
    at com.vectrace.MercurialEclipse.commands.HgUpdateClient$2.run(HgUpdateClient.java:114)
    at com.vectrace.MercurialEclipse.commands.HgUpdateClient$2.run(HgUpdateClient.java:1)
    at com.vectrace.MercurialEclipse.commands.JavaHgCommandJob.doRun(JavaHgCommandJob.java:43)
    at com.vectrace.MercurialEclipse.commands.CommandJob.run(CommandJob.java:89)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)

I suspect an issue with MercurialEclipse and have posted this there already, but after a couple of weeks no one seems to be having this.

But it's not entirely clear what software package is the root cause, as the "unexpected format" also seems to relate to "javahg", which presumably TortoiseHg is using.

Ideas where best to pursue this bug?

Comments (1)

  1. Log in to comment