Master systemvms were built successfully, however, jenkins job fails to push the artifacts to S3. This could be due to a bug in jenkins s3 plugin which is still in open state : https://issues.jenkins-ci.org/browse/JENKINS-27660
We might need to downgrade jenkins s3 plugin for time being. (downgrade to v0.6) Hugo?? ~Talluri On 19/04/15 4:27 pm, "Daan Hoogland" <daan.hoogl...@gmail.com> wrote: >great, all master builds succeed now, only systemvm is unstable. let's >not slack anymore people. Good work Tulari. > >Any volunteers? some builds in other groups are still a problem. > >On Sun, Apr 19, 2015 at 12:02 PM, Srikanteswararao Talluri ><srikanteswararao.tall...@citrix.com> wrote: >> Multi python version issue on slave. Fixed it too Dan. >> >> On 19/04/15 2:06 pm, "Daan Hoogland" <daan.hoogl...@gmail.com> wrote: >> >>>Thanks Talluri, >>> >>>I see the test now passes somewhat further it is not successful yet. >>>the jenkins user cannot access the module urandom. Not sure if this >>>should be fixed in the build job or on the slave. >>> >>>On Sun, Apr 19, 2015 at 8:22 AM, Srikanteswararao Talluri >>><srikanteswararao.tall...@citrix.com> wrote: >>>> Simulator jobs have been failing for a while due to >>>>incompatible/missing python nose plugins. I fixed the jenkins slave and >>>>the jobs to update the marvin for each build. >>>> http://jenkins.buildacloud.org/view/simulator/job/simulator-singlerun/ >>>> >>>> Thanks, >>>> ~Talluri >>> >>> >>> >>>-- >>>Daan >> > > > >-- >Daan
