Hi Amar,
On 28 Jan 2018 06:50, "Amar Tumballi" wrote:
Thanks for this experiment, Xavi!!
I see two proposals here in the thread.
1. Remove unnecessary sleep commands.
2. Try to bring explicit checks, so our tests are more consistent.
I am personally in favor of 1. Lets
Thanks for this experiment, Xavi!!
I see two proposals here in the thread.
1. Remove unnecessary sleep commands.
2. Try to bring explicit checks, so our tests are more consistent.
I am personally in favor of 1. Lets do this.
About 2, as its already discussed, we may get into issues due to many
On Thu, Jan 25, 2018 at 3:03 PM, Jeff Darcy wrote:
>
>
>
> On Wed, Jan 24, 2018, at 9:37 AM, Xavi Hernandez wrote:
>
> That happens when we use arbitrary delays. If we use an explicit check, it
> will work on all systems.
>
>
> You're arguing against a position not taken. I'm
On Wed, Jan 24, 2018, at 9:37 AM, Xavi Hernandez wrote:
> That happens when we use arbitrary delays. If we use an explicit
> check, it will work on all systems.
You're arguing against a position not taken. I'm not expressing
opposition to explicit checks. I'm just saying they don't come for
On Wed, Jan 24, 2018 at 3:11 PM, Jeff Darcy wrote:
>
>
>
> On Tue, Jan 23, 2018, at 12:58 PM, Xavi Hernandez wrote:
>
> I've made some experiments [1] with the time that centos regression takes
> to complete. After some changes the time taken to run a full regression has
>
On Tue, Jan 23, 2018, at 12:58 PM, Xavi Hernandez wrote:
> I've made some experiments [1] with the time that centos regression
> takes to complete. After some changes the time taken to run a full
> regression has dropped between 2.5 and 3.5 hours (depending on the run
> time of 2 tests, see
Hi,
I've made some experiments [1] with the time that centos regression takes
to complete. After some changes the time taken to run a full regression has
dropped between 2.5 and 3.5 hours (depending on the run time of 2 tests,
see below).
Basically the changes are related with delays manually