Coverage tool: handle cases where a ClassCircularityError can still occur #163

rliesenfeld opened this Issue Apr 12, 2015 · 0 comments


1 participant

rliesenfeld commented Apr 12, 2015

There are still cases of certain (unkown) type hierarchies for which a ClassCircularityError can occur from the ClassWriter.getCommonSuperClass(type1, type2) method.

So, we need to either a) discover which cases are these and deal with them; or b) handle the error when it occurs in a way that avoids test failures (ie, simply disregarding the class for coverage), if those cases cannot be found.

@rliesenfeld rliesenfeld added the bug label Apr 12, 2015

@rliesenfeld rliesenfeld self-assigned this Apr 12, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment