+1. On 7/21/16, 9:34 PM, "Venkat Ranganathan" <[email protected]> wrote:
>Thanks Srikanth for giving access to Balu. Last time I looked at the >jobs, there seems to be a dependency on the specific host where it was >running. Trying to move it another host was not helpful. May be we >make it run on a pool of machines than one as it is currently done > >Venkat > >On 7/21/16, 6:58 PM, "Srikanth Sundarrajan" <[email protected]> wrote: > > Hi Balu,Physical access to the machine may be harder. But it is >possible to modify the jenkins job to put out any logs from the build >apart from the binaries it produces. Hopefully that should allow us to >debug this issue. I can either make changes you seek to the build or give >you permissions to modify the job yourself. The later may be a better >choice. > RegardsSrikanth Sundarrajan > > > Subject: Jenkins build failures for Apache Falcon > > From: [email protected] > > To: [email protected] > > Date: Thu, 21 Jul 2016 23:30:08 +0000 > > > > Hi Team, > > > > Recently, builds are failing for Apache Falcon (Email Ref : Build >failed > > in Jenkins: Apache-falcon #1064). The tests that fail require >instances > > scheduled in workflow engine to reach a certain state like RUNNING >or > > SUCCEEDED. But the instances seem to be stuck in state WAITING even >after > > delays of up to 10 seconds. > > > > The same tests do not fail in local environment. The machine running > > Jenkins builds does not seem to have enough resources. I request >access to > > the machine for further debugging and adjusting resource allocation >OR > > will accept help from some one who has access to the machine. > > > > Please let me know, > > Thank you > > Balu Vellanki > > > >
