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
I noticed that Pitest generated a few false mutants, which are equivalent to the original source code, and as a result, they survived. I found a similar previous issue: #497. However, it seems that in certain cases, the fix doesn’t work, or I might be missing some configurations.
Currently using 1.15.0 version with gradle.
public boolean example(int maxSize, Duration maxAge) {
lock.readLock().lock();
try {
int size = elements.size();
if (size == 0) {
return false; // -> replaced boolean return with false for com.example.Example::example → SURVIVED
} else if (size >= maxSize) {
return true; // -> replaced boolean return with true for com.example.Example::example → SURVIVED
} else {
long elapsedNanos = ticker.read() - timeOfLastReset;
return elapsedNanos >= maxAge.toNanos();
}
} finally {
lock.readLock().unlock();
}
}
}
Is there a config missing at our side or is it a known bug?
The text was updated successfully, but these errors were encountered:
Hi,
I noticed that Pitest generated a few false mutants, which are equivalent to the original source code, and as a result, they survived. I found a similar previous issue: #497. However, it seems that in certain cases, the fix doesn’t work, or I might be missing some configurations.
Currently using
1.15.0
version with gradle.Is there a config missing at our side or is it a known bug?
The text was updated successfully, but these errors were encountered: