Task #2750
Jenkins FPE should be disabled for 2018 branch
Description
There are known issues that trigger FPE events, but the false positives for unrelated code are more of a problem than failing to detect any new bugs we might introduce that the FPE checks would notice.
Associated revisions
History
#1 Updated by Gerrit Code Review Bot 5 months ago
Gerrit received a related patchset '1' for Issue #2750.
Uploader: Mark Abraham (mark.j.abraham@gmail.com)
Change-Id: gromacs~release-2018~I12c5e1a08e43e48cb7012edb6d5e8aea08baddc8
Gerrit URL: https://gerrit.gromacs.org/8674
#2 Updated by Mark Abraham 5 months ago
- Status changed from New to Fix uploaded
#3 Updated by Mark Abraham 5 months ago
- Status changed from Fix uploaded to Resolved
Applied in changeset 03737b0cafac0fbe7445e291c418756ec5f7365b.
#4 Updated by Mark Abraham 4 months ago
- Status changed from Resolved to Closed
Disabled FPE checking for non-release builds
This means that Jenkins will no longer give any reports, false or
true, from floating-point exceptions. Test binaries can still have FPE
checking enabled manually, however.
The content of this change should not be merged into the release-2019
branch.
Fixes #2750
Change-Id: I12c5e1a08e43e48cb7012edb6d5e8aea08baddc8