You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you manually delete the compiled test class from the target directory at tmp/lang29-buggy/target/test-classes/org/apache/commons/lang3/SystemUtilsTest.class, the test will pass:
$ defects4j/framework/bin/defects4j test -w tmp/lang29-buggy
Failing tests: 0
The text was updated successfully, but these errors were encountered:
I first encountered this issue on a WSL Ubuntu 20.04 installation on Windows 10. Java version was 1.8.0_332 Temurin installed using SDKMAN. Now the same system is updated to Ubuntu 22.04 with Java 1.8.0_345 Temurin, and the problem is still reproducible. Maven is 3.8.6.
I checked the issue on the latest Manjaro Linux update and Pop!_OS 22.04 with the same Java 8 version, and it still happened. There is no separate Ant or Maven installation on these systems.
I've seen this behavior on other random Java projects. I guess that's why people obsessively clean compile their projects.
There is a problem with Lang 29 where if you compile and test the buggy checkout, patching it next won't change the test result.
Steps to reproduce
tmp/lang29-buggy/src/main/java/org/apache/commons/lang3/SystemUtils.java
, line 1672 and fix the issue:If you manually delete the compiled test class from the target directory at
tmp/lang29-buggy/target/test-classes/org/apache/commons/lang3/SystemUtilsTest.class
, the test will pass:The text was updated successfully, but these errors were encountered: