4.2.1 automation not executed from jenkins.buildacloud.org,

Automation executed in side my company including vmware, 

Regards,
Rayees 

-----Original Message-----
From: Sebastien Goasguen [mailto:run...@gmail.com] 
Sent: Friday, November 08, 2013 12:20 AM
To: dev@cloudstack.apache.org
Subject: Re: 4.2.1 BVT automation results


On Nov 7, 2013, at 9:54 AM, Rayees Namathponnan 
<rayees.namathpon...@citrix.com> wrote:

> Hi Sebastian,
> 
> I don't think so we are running automation  4.2.1 branch in 
> jenkins.buildacloud.org,  below result is from master branch; 
> 

So how did you come up with the results for the 4.2.1 branch ?

> http://jenkins.buildacloud.org/view/cloudstack-qa/job/test-smoke-matrix/ 
> 
> Also I reported master failures in ASF jira
> 
> https://issues.apache.org/jira/browse/CLOUDSTACK-5050 
> https://issues.apache.org/jira/browse/CLOUDSTACK-5049 
> https://issues.apache.org/jira/browse/CLOUDSTACK-5047 
> https://issues.apache.org/jira/browse/CLOUDSTACK-5046 
> https://issues.apache.org/jira/browse/CLOUDSTACK-5045 
> https://issues.apache.org/jira/browse/CLOUDSTACK-4835 
> 
> 
> NOTE : I ran automation with RHEL 6.3 
> 
> Regards,
> Rayees 
> 
> -----Original Message-----
> 
> From: Sebastien Goasguen [mailto:run...@gmail.com] 
> Sent: Thursday, November 07, 2013 12:29 AM
> To: dev@cloudstack.apache.org
> Subject: Re: 4.2.1 BVT automation results
> 
> 
> On Nov 6, 2013, at 6:07 PM, Rayees Namathponnan 
> <rayees.namathpon...@citrix.com> wrote:
> 
>> Hi All,
>> 
>> 4.2.1 BVT automation results published to cwiki; you can see the results 
>> below
>> 
>> https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.2.1+Automation+Result
>> 
>> Regards,
>> Rayees
>> 
> 
> Where are those results coming from ?
> 
> The qa and simulator jobs on http://jenkins.buildacloud.org/view/simulator/ 
> seem to have been failing for a while 
> 
> Also it would be great if the results table could have the OS version. 
> Technically we need to have each set run on ubuntu 12.04 and Centos6.4.
> 
> -sebastien
> 
> 
>> 
> 

Reply via email to