Skip to content

Conversation

@lucasccordeiro
Copy link
Contributor

check whether the java bytecode index matches for the existing coverage goals/

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

get_java_bytecode_index should only be compared when using a Java analysis

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now we check whether get_java_bytecode_index is empty.

@lucasccordeiro lucasccordeiro force-pushed the test-gen-support-fix-issue-15 branch 2 times, most recently from 77a5646 to 00cb2b0 Compare April 5, 2017 15:36
Copy link
Contributor

@mgudemann mgudemann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please squash commits after the changes

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as compare returns an int, could you test on 0 here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as above

@mgudemann
Copy link
Contributor

there is also compile failures on travis, please fix those, too

check whether the java bytecode index matches for the existing
coverage goals
@lucasccordeiro lucasccordeiro force-pushed the test-gen-support-fix-issue-15 branch from aed785c to 2d7b34a Compare April 6, 2017 15:50
@lucasccordeiro
Copy link
Contributor Author

Due to several merge conflicts, I have created another PR to handle this issue: #772

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

Successfully merging this pull request may close these issues.

2 participants