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: bvella...@hortonworks.com
> To: dev@falcon.apache.org
> 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
>
