Re: Extensions team hijack into Apache workers

2019-05-08 Thread Anthony Baker
> On May 7, 2019, at 3:28 PM, Scott Jewell wrote: > > Hi, > > Not sure if this is the right place to go, but the GemFire Extensions team > would like to be able to hijack into the Apache pipeline workers. I’ll point out that company affiliation has no bearing on whether this request is grante

Re: Extensions team hijack into Apache workers

2019-05-07 Thread Jacob Barrett
I assume you’ve tied running the hanging test locally. When the tests time out in the CI there should be a stackdump file that is collected and uploaded into GCS. The link to download it is at the end of the job. Have you checked this file? -Jake > On May 7, 2019, at 4:16 PM, Scott Jewell wr

Re: Extensions team hijack into Apache workers

2019-05-07 Thread Scott Jewell
Hi Jacob, The particular case I was interested in was to be able to inspect member logs while tests were running. We had a case where a long running test was occasionally hanging. We wanted to be able peek at the logs in an attempt to determine if the test was making progress or had hung. It sou

Re: Extensions team hijack into Apache workers

2019-05-07 Thread Jacob Barrett
Why are you asking to hijack a worker? Workers do not perform any builds or tests as all of this is offloaded to the heavy lifter VMs. These VMs are transient and can’t be accessed after a job is complete. -jake > On May 7, 2019, at 3:28 PM, Scott Jewell wrote: > > Hi, > > Not sure if this

Extensions team hijack into Apache workers

2019-05-07 Thread Scott Jewell
Hi, Not sure if this is the right place to go, but the GemFire Extensions team would like to be able to hijack into the Apache pipeline workers. When attempting to access the workers, we get the following error: fly -t apache hijack -u= https://concourse.apachegeode-ci.info/teams/main/pipelines/