René Just

Hi @VinayKabadi, You can access the entire (git) history, using the original buggy and fixed commit hashes (e.g., see revision ids in `active-bugs.csv`). Given your use case, you can also...

@pwcwmy Are you running `defects4j compile` or something else? Also, is there are reason for why you are using Defects4J 1.2 (as opposed to a more recent version)?

Hi @hh-wq, It looks like the post-checkout step, which creates these additional git tags, is failing. As a result, subsequent steps also fail. Since Defects4J does not officially support Windows,...

Hi @SaraBaradaran, Defects4J v2 and v3 use different Java versions to compile the artifacts, which probably explains the difference in the IR (explicit use of StringBuilder vs. dynamic invoke for...

Hi @danielding110, After running `defects4j test` the detailed test failures are available in `/failing_tests`. This file uses the same format as the ones in the `trigger_tests` directory. For example: ```...