| Re: [cdt-dev] Test failures for RC4 |
|
Yes, discussing things with Marc-Andre, it seems that the failure happened due to the upgrade and not the commit. Sorry about that.
So we have two failures linked to our new HIPP. The Standalone test passes on my machine though, which is a good sign. I suggest ignoring these two failures and taking RC4 anyway, but still trying to get those tests to pass for later.
Any objections? From: cdt-dev-bounces@xxxxxxxxxxx <cdt-dev-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
Sent: September 12, 2016 2:52 PM To: CDT General developers list. Subject: Re: [cdt-dev] Test failures for RC4 Actually looking at the managed build test, looks like we’re now using a
different version of gcc for this test, which we would with the OS upgrade. BTW, that brings up the need for running our tests in controlled environments such as you get with Docker. Would be great to investigate that. Doug. On 2016-09-12, 2:40 PM, "Doug Schaefer" <dschaefer@xxxxxxxxxxxxxx> wrote: >On 2016-09-12, 2:30 PM, "cdt-dev-bounces@xxxxxxxxxxx on behalf of Marc >Khouzam" <cdt-dev-bounces@xxxxxxxxxxx on behalf of >marc.khouzam@xxxxxxxxxxxx> wrote: > >>Hi, >> >>I get two consistent test failures for 9.1. >> >>The first is >>org.eclipse.cdt.managedbuilder.core.tests.ManagedProject30MakefileTests.t >>e >>stSpaces >> >>which seems to have always failed for the patch of commit >>5a1828f37defe1e4852fcaa29a77ec28d2c1ac83 >> "Fix scanner info cache to properly refresh resource commands." >> >>My guess is that this failure was not noticed because our tests are so >>often flaky that we don't >>pay much attention to failures anymore. But from what I can see, it >>might be a real one. > >Though you¹d have to draw a link from the Core Build scanner info system >to Managed Build which is totally separate. I couldn¹t so I left it. > >But yes, our tests at this moment are junk since we can¹t know whether a >change actually breaks anything and I¹m not going to waste my time unless >I have a feeling that I broke something. > >Doug. > >> >>The second failure is >>org.eclipse.cdt.debug.application.tests.StandaloneTest1.org.eclipse.cdt.d >>e >>bug.application.tests.StandaloneTest1 >>and I'm wondering if it is not caused by our HIPP upgrade which caused >>some UI issues recently. >> >>Any help would be appreciated as we need to get this build out the door. >> >>Thanks >> >>Marc >>_______________________________________________ >>cdt-dev mailing list >>cdt-dev@xxxxxxxxxxx >>To change your delivery options, retrieve your password, or unsubscribe >>from this list, visit >>https://dev.eclipse.org/mailman/listinfo/cdt-dev
> _______________________________________________ cdt-dev mailing list cdt-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cdt-dev | ||