Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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


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:
>>I get two consistent test failures for 9.1.
>>The first is 
>>which seems to have always failed for the patch of commit
>>    "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.
>>The second failure is
>>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.
>>cdt-dev mailing list
>>To change your delivery options, retrieve your password, or unsubscribe
>>from this list, visit

Back to the top