René Just
René Just
@claudeyj, thanks for reporting this! I agree that test failures should all be logged instead of failing the build. From the output, it looks like the exception is raised in...
@markro49 @mernst Looks like this change would be in line with other changes we made to ensure reproducibility for Java 11. If this change allows us to remove the requirement...
Hi @Coppelian The build files in Defects4J are hierarchical (to cover a wide range of projects and a wide range of versions for each project): defects4j.build.xml -> -> build.xml You...
@JyotirS20, [Figure 2 in the Defects4J paper](https://homes.cs.washington.edu/~rjust/publ/defects4j_issta_2014.pdf) visualizes the bug-mining process. I believe what you are asking is whether any of the bugs in Defects4J may have tests added in...
@Judgh Defects4J v2 (current version) requires Java 8. Defects4J v3 (to be released soon) will support Java 11.
Related to partial and multi-commit bugs (#619).
Similar to issue #619, we would welcome contributions that add metadata for the bugs in the dataset. What constitutes a bug vs. a feature is a tricky question, though. For...
Hi @hellojg123, Just to clarify: are you observing (in the most recent version of Defects4J) failing tests that do not cover any buggy lines? If so, can you please provide...
Hi @zeyugao, This observation is aligned with the bug-mining approach used to curate the dataset. Multi-commit bugs are certainly interesting, and we would welcome contributions that add these types of...
I was also unable to reproduce this in version 3. Closing this issue.