[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Intermittend test failures on HIPP
|
You only need one committer to +1 the verify. If you see the test is unrelated to your change, just do that.
The intermittent failures are a pain in the behind. We really need to make tests more deterministic.
Sent from my BlackBerry Z30 smartphone.
Original Message
From: Marc Khouzam
Sent: Friday, December 13, 2013 9:34 AM
To: 'CDT General developers list.'
Reply To: CDT General developers list.
Subject: Re: [cdt-dev] Intermittend test failures on HIPP
> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On Behalf Of Paul Webster
> Sent: Friday, December 13, 2013 9:08 AM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Intermittend test failures on HIPP
>
> We've been encountering the same thing. What I usually do is retrigger the
> failing job (creating another and clearing the bit).
> If it passes a second time
> then your gold. If you have the same kind of errors, then you need to
> retrigger again and you can merge it before Hudson CI determines another
> pass/fail.
That is a quick way to get around it. I hadn't realized one can do that. Thanks!
> Other things you can try is to have 2 committers +1 the verify (and see if that
> overrides the single -1) or slightly update the change and push it for review,
> the new patch set will clear the bit.
That is the one I wanted to avoid, it is more cumbersome :)
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
