Re: [cdt-dev] gerrit verifier job timing

[Marc Khouzam <marc.khouzam@xxxxxxxxxxxx>]

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> 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]
Received: Wednesday, 18 Feb 2015, 19:56
To: CDT General developers list. [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