ter?
>
> Best Regards,
> Sanjeev N
> Chief Product Engineer, Accelerite
> Off: +91 40 6722 9368 | EMail: sanjeev.neelar...@accelerite.com
>
>
> -Original Message-
> From: Remi Bergsma [mailto:rberg...@schubergphilis.com]
> Sent: Monday, March 28, 2016 1:24 PM
> To:
[mailto:rberg...@schubergphilis.com]
Sent: Monday, March 28, 2016 1:24 PM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] PR testing process
Indeed. If a merge fails then you'll not be able to merge it to master or
another release branch later on anyway so the author must rebase against the
Indeed. If a merge fails then you'll not be able to merge it to master or
another release branch later on anyway so the author must rebase against the
base branch first. No need spending test cycles on that.
Most likely github already reports that PR as 'unstable' so you could also
check for t
;"
> mailto:dev@cloudstack.apache.org>>
> Date: Monday 28 March 2016 at 09:05
> To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
> mailto:dev@cloudstack.apache.org>>
> Subject: [DISCUSS] PR testing process
>
> Hi,
>
> Curre
Hi Sanjeev,
Thanks for bringing this up.
This is happening because the PR code and the master have deviated since the pr
has been created(assuming that PR was rebased with master at the time of
creation) and we start testing it. Ideally we should start testing as soon as
the pr is created but
;
Date: Monday 28 March 2016 at 09:05
To: "dev@cloudstack.apache.org<mailto:dev@cloudstack.apache.org>"
mailto:dev@cloudstack.apache.org>>
Subject: [DISCUSS] PR testing process
Hi,
Currently CI is picking the code from the PR branch, which may or may not be
rebased with
Hi,
Currently CI is picking the code from the PR branch, which may or may not be
rebased with latest master. This is causing test failures even though they were
fixed in latest master.
e.g.: test_vpc_site2site_vpn.
Error Message
local variable 'vm1' referenced before assignment.
There were few
