We've reconfigured our ci to be re-triggered only on command
"retrigger murano-ci" for exactly this reason. But, I guess that it'll
take a lot of time to convince all 3rd party CI systems to do the same
and to use the same trigger keyword. So, maybe it'll be easier to
update OpenStack CI configura
Right, and even if we did change all the 3rd parties over to something
that doesn't start with 'recheck' there will be inconsistencies between
3rd parties and 1st party.
If you can retrigger all systems (1st or 3rd) in the same way it'll be
much easier for users. For example, if you see "reche
On 2014-08-12 17:43:37 +1000 (+1000), Joshua Hesketh wrote:
> Right, and even if we did change all the 3rd parties over to
> something that doesn't start with 'recheck' there will be
> inconsistencies between 3rd parties and 1st party.
[...]
If this is really something the various CI operators wan
On 08/12/2014 07:17 AM, Jeremy Stanley wrote:
> On 2014-08-12 17:43:37 +1000 (+1000), Joshua Hesketh wrote:
>> Right, and even if we did change all the 3rd parties over to
>> something that doesn't start with 'recheck' there will be
>> inconsistencies between 3rd parties and 1st party.
> [...]
>
>
Hi,
I'm looking at Sean's change to run more of tempest on F20 [1]. To
test it I'm using [2] -- it has shown is that tempest on F20 is *way*
slower than on Ubuntu, to the point it times out.
I compared logs from [3] & [4] to come up with a comparison [5],
e.g. SecurityGroupsTestXML.test_server_s
On 13 August 2014 17:23, Ian Wienand wrote:
> Hi,
>
> I'm looking at Sean's change to run more of tempest on F20 [1]. To
> test it I'm using [2] -- it has shown is that tempest on F20 is *way*
> slower than on Ubuntu, to the point it times out.
>
> I compared logs from [3] & [4] to come up with a
