| Summary: | JUnit failure in Hudson builds - ManagedBuildCoreTests20.testScannerInfoInterface | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Andrew Gvozdev <angvoz.dev> |
| Component: | cdt-build | Assignee: | Andrew Gvozdev <angvoz.dev> |
| Status: | RESOLVED FIXED | QA Contact: | Andrew Gvozdev <angvoz.dev> |
| Severity: | normal | ||
| Priority: | P3 | CC: | recoskie |
| Version: | 7.0 | ||
| Target Milestone: | 7.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Andrew Gvozdev
Chris, I reverted your change in DescriptionScannerInfoProvider back to 1.11 as it makes the test fail. I did not notice this reversion till now. The bugzilla description didn't indicate the problem. The code does need to change because blindly running toOSString() on every discovered path totally messes things up for remote projects. I plan on reverting the fix but I'll have a look at the tests to make sure they continue to pass. I will file a separate bugzilla for the issue the original fix was meant to address. *** cdt cvs genie on behalf of agvozdev *** bug 312812: JUnit failure in Hudson builds - ManagedBuildCoreTests20.testScannerInfoInterface Reverted to 1.11 as the last revision broke JUnit test [*] DescriptionScannerInfoProvider.java 1.13 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/all/org.eclipse.cdt.core/model/org/eclipse/cdt/internal/core/settings/model/DescriptionScannerInfoProvider.java?root=Tools_Project&r1=1.12&r2=1.13 |