Re: [cdt-dev] Final build for CDT 8.0

[Chris Recoskie <recoskie@xxxxxxxxxx>]

Well someone added more test cases to the GNU parser, the LR parser derives its testcases from the GNU testcases, so they just get picked up automatically, but these test cases are failing because the LR parser was not updated with the same bug fix that went into the GNU parser, which is what the tests are testing.

John intends to fix the bugs that these tests say we have, but has not had the opportunity yet, and won't for a while. We can override these if you like so that the build shows "green" instead of "yellow" but we will be masking actual bugs then.

===========================
Chris Recoskie
Team Lead, IBM CDT and RDT
IBM Toronto

Andrew Gvozdev ---06/02/2011 03:42:10 PM---What is wrong with JUnit test cases? https://hudson.eclipse.org/hudson/job/cdt-nightly/lastCompleted

From:	Andrew Gvozdev <angvoz.dev@xxxxxxxxx>
To:	"CDT General developers list." <cdt-dev@xxxxxxxxxxx>, Chris Recoskie/Toronto/IBM@IBMCA, John Liu <john_ws_liu@xxxxxxxxx>
Date:	06/02/2011 03:42 PM
Subject:	Re: [cdt-dev] Final build for CDT 8.0

---

What is wrong with JUnit test cases? https://hudson.eclipse.org/hudson/job/cdt-nightly/lastCompletedBuild/testReport/

If not for those the release would be clean as far as unit test cases. Is it still possible to fix them? What was the point of adding those if you are not maintaining them?


>>> org.eclipse.cdt.core.lrparser.tests.LRCompletionBasicTest.testCompletionInSizeof340664 0.069
>>> org.eclipse.cdt.core.lrparser.tests.LRGCCCompleteParseExtensionsTest.testTypetraits_Bug342683 0.00409
>>> org.eclipse.cdt.core.lrparser.tests.LRTemplateTests.testTemplateIDAmbiguity_341747a 0.0169
>>> org.eclipse.cdt.core.lrparser.tests.LRTemplateTests.testTemplateIDAmbiguity_341747b 0.0179
>>> org.eclipse.cdt.core.lrparser.tests.LRTemplateTests.testTemplateIDAmbiguity_341747c 0.0169
>>> org.eclipse.cdt.core.lrparser.tests.LRTemplateTests.testTemplateIDAmbiguity_341747d 0.0189
>>> org.eclipse.cdt.core.parser.upc.tests.UPCCompletionBasicTest.testCompletionInSizeof340664 0.0659
>>> org.eclipse.cdt.core.parser.xlc.tests.base.XlcLRCompletionBasicTest.testCompletionInSizeof340664 0.0339
>>> org.eclipse.cdt.core.parser.xlc.tests.base.XlcLRGCCCompleteParseExtensionsTest.testTypetraits_Bug342683 0.00509
>>> org.eclipse.cdt.core.parser.xlc.tests.base.XlcLRTemplateTests.testTemplateIDAmbiguity_341747a 0.0169
>>> org.eclipse.cdt.core.parser.xlc.tests.base.XlcLRTemplateTests.testTemplateIDAmbiguity_341747b 0.0169
>>> org.eclipse.cdt.core.parser.xlc.tests.base.XlcLRTemplateTests.testTemplateIDAmbiguity_341747c 0.0169
>>> org.eclipse.cdt.core.parser.xlc.tests.base.XlcLRTemplateTests.testTemplateIDAmbiguity_341747d 0.0189


Thanks,
Andrew

On Thu, Jun 2, 2011 at 2:49 PM, Schaefer, Doug <Doug.Schaefer@xxxxxxxxxxxxx> wrote:

Hey gang,

 

Just a reminder that tomorrow’s build is the last one for CDT 8.0 assuming a perfect world J. Of course we’ll have respins but starting tomorrow, they should only be for emergency fixes. We will start feeding the builds to the Indigo repository and EPP packages on Monday. Again hopefully that is it, but we do have contingency if absolutely necessary.

 

The release goes live on Wed, June 22. Shortly, if not immediately after that we’ll kick off the transition to git. And only then will we create the branch for CDT 8.0.x and allow work to continue towards Juno on master. That should give everyone time to try out git on the test repo and ask the experts we have around questions so that we’re ready hit the ground running when it’s ready.

 

Let us know if you have questions/concerns,

Doug.

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev