Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error on running Auto tuning #17

Open
aabhasb opened this issue Nov 26, 2018 · 2 comments
Open

Error on running Auto tuning #17

aabhasb opened this issue Nov 26, 2018 · 2 comments
Assignees

Comments

@aabhasb
Copy link

aabhasb commented Nov 26, 2018

I tried to run the auto-tuned mode by using a combination of line based and structured. I was performing my experiments over the curated DrJava source code made available from the first JDime evaluations. I was running the tool in the following manner - "JDime -r -m linebased,structured -f -o mergeDir LeftDIr BaseDir RightDir "

I keep getting the following error:
java.lang.RuntimeException: beaver.Scanner$Exception: illegal escape sequence "'\u"
at de.fosd.jdime.util.parser.Parser.getTokenCount(Parser.java:184)"
As a result of this error, the tool falls back to line based approach "JDime [20:05:28] SEVERE: Falling back to line based strategy. "

I thought this is a windows issue and how it uses "" for directory separators so I tried the same command in Linux and through Eclipse by using "\" but I kept getting the same error. Oddly, this does not happen when I pass either only linebased or only structured as the mode.

Attached is the stack trace

stacktrace.txt

@GSeibt
Copy link
Collaborator

GSeibt commented Dec 18, 2018

Alright, so when using the combined strategy (-m A,B) the code resulting from using strategy A is parsed to determine whether there were conflicts and strategy B needs to be tried. This parsing is done as part of statistics collection and thus includes having ExtendJ count the number of tokens in the code. That fails in ExtendJ, not in our code. Apparently the merge result contains character escape sequences that ExtendJ can't handle.

Could you please attach the directories that you were merging? Might be that a more recent ExtendJ version resolves the issue.

@GSeibt GSeibt assigned GSeibt and xai Dec 18, 2018
@aabhasb
Copy link
Author

aabhasb commented Dec 23, 2018

I tried running Jdime from CMD and from bash shell. Hence, I passed the following directories respectively:
D:\mergedProjects\completed\DrJava\rev3734-3786\base-trunk-3734
/mnt/d/mergedProjects/completed/DrJava/rev3734-3786/base-trunk-3734$

Also, I noted the combined strategy works when I work on a single file, it fails when I use the '-r' option for a recursive merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants