mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-04-29 19:45:01 +02:00
![]() The test used to fail on the -100.0 / 3.0 case if that was the first condition tested. This change forces that to not be the first condition tested which reduces the incidence of failures. This does not resolve the unknown underlying issue which appears to be on the GDB side that CDT is exposing. Upgrading GDB version may also resolve the test failures, but for now I am going with this fix so that we stop having UNSTABLE Jenkins CI builds. Change-Id: Ibfa93a8350cfc08adf721723bc07566521bed812 |
||
---|---|---|
.. | ||
org.eclipse.cdt.dsf.gdb | ||
org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui | ||
org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui.tests | ||
org.eclipse.cdt.dsf.gdb.tests | ||
org.eclipse.cdt.dsf.gdb.ui | ||
org.eclipse.cdt.examples.dsf.gdb | ||
org.eclipse.cdt.gnu.dsf-feature | ||
org.eclipse.cdt.gnu.multicorevisualizer-feature | ||
org.eclipse.cdt.tests.dsf.gdb | ||
pom.xml |