Re: jenkins.impala.io pre-existing workspace

https://issues.apache.org/jira/browse/IMPALA-5959 On Tue, Sep 19, 2017 at 2:54 PM, Jim Apple wrote: > Nobody did. > > On Tue, Sep 19, 2017 at 2:29 PM, Matthew Jacobs wrote: > >> Did anyone file a JIRA for this? I saw this again. >> >> On Thu, Aug 31,

Re: jenkins.impala.io pre-existing workspace

Nobody did. On Tue, Sep 19, 2017 at 2:29 PM, Matthew Jacobs wrote: > Did anyone file a JIRA for this? I saw this again. > > On Thu, Aug 31, 2017 at 1:36 PM, Jim Apple wrote: > > Also, to be clear, I don't have the cycles to lead the fix-the-cleanup > >

Re: jenkins.impala.io pre-existing workspace

Did anyone file a JIRA for this? I saw this again. On Thu, Aug 31, 2017 at 1:36 PM, Jim Apple wrote: > Also, to be clear, I don't have the cycles to lead the fix-the-cleanup > task at the moment. > > On Wed, Aug 30, 2017 at 4:45 PM, Jim Apple wrote:

Re: jenkins.impala.io pre-existing workspace

Also, to be clear, I don't have the cycles to lead the fix-the-cleanup task at the moment. On Wed, Aug 30, 2017 at 4:45 PM, Jim Apple wrote: > The workspace cleanup isn't working - see the last bit of any recent > ub1604 job: >

Re: jenkins.impala.io pre-existing workspace

The layout of #6 has served me well for a year now. It allows me to keep several such workspaces around to work with different Impala versions, I just have to be control carefully which workspace the minicluster runs from -- but that's not an issue here. On Thu, Aug 31, 2017 at 2:44 AM, Philip

Re: jenkins.impala.io pre-existing workspace

On Wed, Aug 30, 2017 at 4:45 PM, Jim Apple wrote: > The workspace cleanup isn't working - see the last bit of any recent > ub1604 job: https://jenkins.impala.io/view/Utility/job/ubuntu-16.04- > from-scratch/206/console > > 03:56:40.920 [WS-CLEANUP] Deleting project

Re: jenkins.impala.io pre-existing workspace

The workspace cleanup isn't working - see the last bit of any recent ub1604 job: https://jenkins.impala.io/view/Utility/job/ubuntu-16.04-from-scratch/206/console 03:56:40.920 [WS-CLEANUP] Deleting project workspace...Cannot delete workspace :remote file operation failed: /home/ubuntu at

Re: jenkins.impala.io pre-existing workspace

Looks like someone has done this. On Wed, Aug 23, 2017 at 8:16 PM, Alexander Behm wrote: > Yes, let's please add the post-build action for sanity and consistency with > our other jobs. > > On Wed, Aug 23, 2017 at 7:42 PM, Tim Armstrong > wrote:

Re: jenkins.impala.io pre-existing workspace

Yes, let's please add the post-build action for sanity and consistency with our other jobs. On Wed, Aug 23, 2017 at 7:42 PM, Tim Armstrong wrote: > Maybe the workspace just got left in a weird state - I think in most cases > "git init" followed by checking out a branch

Re: jenkins.impala.io pre-existing workspace

Maybe the workspace just got left in a weird state - I think in most cases "git init" followed by checking out a branch and doing a clean would work. Should we add the delete workspace post-build action? On Wed, Aug 23, 2017 at 5:32 PM, Michael Brown wrote: > Not a known

Re: jenkins.impala.io pre-existing workspace

Not a known issue. I noticed ubuntu-16.04-from-scratch is not set to clean up its workspace, and its config has not been touched since Aug 11. It seems strange we only saw this now On Wed, Aug 23, 2017 at 5:25 PM, Tim Armstrong wrote: > Is this a known problem? My

jenkins.impala.io pre-existing workspace

Is this a known problem? My job failed because the Impala repo already existed on the machine: https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/164/ *23:00:24* + /usr/bin/git init /home/ubuntu/Impala*23:00:24* Reinitialized existing Git repository in /home/ubuntu/Impala/.git/