Re: [cdt-dev] gerrit verifier job timing

[Doug Schaefer <dschaefer@xxxxxxx>]

+1 from me too, but no, there isn’t a way to do that AFAIK.

Doug.

From: Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Thursday, February 19, 2015 at 1:25 PM
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] gerrit verifier job timing

+1. There is also no need to run core tests if only UI plugins were modified.

-sergey

On Thu, Feb 19, 2015 at 10:21 AM, Nathan Ridge <zeratul976@xxxxxxxxxxx> wrote:

Is it possible to condition what test suites are run, on what source directories are modified by the patch? Then we could e.g. only run the debug tests for patches that modify the debug folders.

Regards,
Nate

________________________________
> From: marc.khouzam@xxxxxxxxxxxx
> To: elaskavaia.cdt@xxxxxxxxx
> Date: Thu, 19 Feb 2015 14:43:24 +0000
> CC: cdt-dev@xxxxxxxxxxx
> Subject: Re: [cdt-dev] gerrit verifier job timing
>
> Along the lines of what Doug was saying, we probably don't gain much by
> running the debug tests in the verify job.
>
> Unless the debug plugins are being changed, there is very little value
> in running those tests in the verify job anyway.
>
> Internally we only run a very small subset of the debug test in a
> verify job; but that also verifies we didn't break GDB. It probably
> isn't even that valuable for CDT.
>
> So with the nightly jobs running the debug tests I'm in favor of
> removing them from the verify job. I'd like to see if others are of the
> same opinion.
>
> Marc
>
>
>
>
> -----Original Message-----
> From: Alena Laskavaia [elaskavaia.cdt@xxxxxxxxx]
> Received: Thursday, 19 Feb 2015, 8:31
> To: Marc Khouzam [marc.khouzam@xxxxxxxxxxxx]
> CC: cdt-dev@xxxxxxxxxxx [cdt-dev@xxxxxxxxxxx]
> Subject: Re: [cdt-dev] gerrit verifier job timing
>
> I started doing it. Need to review all ui tests and remove all sleeps.
> Debugger tests are the worst, takes 10 min.
>
> On Wed, Feb 18, 2015 at 10:32 PM, Marc Khouzam
> <marc.khouzam@xxxxxxxxxxxx<mailto:marc.khouzam@xxxxxxxxxxxx>> wrote:
> If we can first speed up the tests, that would be great. It would be
> good to know which tests are the longest to know where to focus.
>
> If we can't easily get that info from the complete build, we could run
> the tests for each relevant plugin independently and look at how long
> each plugin takes.
>
> We could do this easily with a little script on a local machine.
>
> Marc
>
>
>
> -----Original Message-----
> From: Alena Laskavaia
> [elaskavaia.cdt@xxxxxxxxx<mailto:elaskavaia.cdt@xxxxxxxxx>]
> Received: Wednesday, 18 Feb 2015, 19:56
> To: CDT General developers list.
> [cdt-dev@xxxxxxxxxxx<mailto:cdt-dev@xxxxxxxxxxx>]
> Subject: [cdt-dev] gerrit verifier job timing
>
> Gerrit verifier job now takes 44 min. This is too much IMHO.
> This type of job should take at most 15 min. Hudson now is constantly
> backed up
> with multiple jobs and with constant need for rebase reviews its even worse.
> Buy the time verifier finished I need to rebase again!
> So we have few options
> - you disagree with me and we do nothing
> - we try to optimize tests and see why its taking so long
> - we split test into two tiers - tier1 - runs with gerrit verifier,
> tier2 (and tier1) - runs with official nightly build (or branch
> builds), all commiters involved in changes for the build get email if
> it fails tests
>
>
> _______________________________________________ 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