./gridworks test fails with "Cannot change ownership" error

[GoogleCodeExporter]

./gridworks test

r683 on Windows XP, Cygwin 1.7, Java JDK 1.6u20 returns the below error.  I 
think it is to do with permissions when writing to a folder (running 
without admin rights):

tar: virtualenv-1.4.6/virtualenv.egg-info/not-zip-safe: Cannot change 
ownership
to uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/virtualenv.egg-info/top_level.txt: Cannot change 
ownership
 to uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/virtualenv.egg-info/entry_points.txt: Cannot change 
owners
hip to uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/virtualenv.egg-info/PKG-INFO: Cannot change ownership 
to u
id 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/virtualenv.egg-info/dependency_links.txt: Cannot 
change ow
nership to uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/virtualenv.egg-info/SOURCES.txt: Cannot change 
ownership t
o uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/virtualenv.egg-info: Cannot change ownership to uid 
1000,
gid 1000: Invalid argument
tar: virtualenv-1.4.6/docs/index.txt: Cannot change ownership to uid 1000, 
gid 1
000: Invalid argument
tar: virtualenv-1.4.6/docs/news.txt: Cannot change ownership to uid 1000, 
gid 10
00: Invalid argument
tar: virtualenv-1.4.6/docs/license.txt: Cannot change ownership to uid 
1000, gid
 1000: Invalid argument
tar: virtualenv-1.4.6/docs/_build/_sources/index.txt: Cannot change 
ownership to
 uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/docs/_build/_sources/news.txt: Cannot change 
ownership to
uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/docs/_build/_sources/license.txt: Cannot change 
ownership
to uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/docs/_build/_sources: Cannot change ownership to uid 
1000,
 gid 1000: Invalid argument
tar: virtualenv-1.4.6/docs/_build: Cannot change ownership to uid 1000, gid 
1000
: Invalid argument
tar: virtualenv-1.4.6/docs: Cannot change ownership to uid 1000, gid 1000: 
Inval
id argument
tar: virtualenv-1.4.6/scripts/virtualenv: Cannot change ownership to uid 
1000, g
id 1000: Invalid argument
tar: virtualenv-1.4.6/scripts: Cannot change ownership to uid 1000, gid 
1000: In
valid argument
tar: virtualenv-1.4.6/PKG-INFO: Cannot change ownership to uid 1000, gid 
1000: I
nvalid argument
tar: virtualenv-1.4.6/MANIFEST.in: Cannot change ownership to uid 1000, gid 
1000
: Invalid argument
tar: virtualenv-1.4.6/setup.cfg: Cannot change ownership to uid 1000, gid 
1000:
Invalid argument
tar: virtualenv-1.4.6/setup.py: Cannot change ownership to uid 1000, gid 
1000: I
nvalid argument
tar: virtualenv-1.4.6/virtualenv.py: Cannot change ownership to uid 1000, 
gid 10
00: Invalid argument
tar: virtualenv-1.4.6/virtualenv_support/setuptools-0.6c11-py2.6.egg: 
Cannot cha
nge ownership to uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/virtualenv_support/setuptools-0.6c11-py2.5.egg: 
Cannot cha
nge ownership to uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/virtualenv_support/setuptools-0.6c11-py2.4.egg: 
Cannot cha
nge ownership to uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/virtualenv_support/pip-0.6.3.tar.gz: Cannot change 
ownersh
ip to uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/virtualenv_support/distribute-0.6.8.tar.gz: Cannot 
change
ownership to uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/virtualenv_support/__init__.py: Cannot change 
ownership to
 uid 1000, gid 1000: Invalid argument
tar: virtualenv-1.4.6/virtualenv_support: Cannot change ownership to uid 
1000, g
id 1000: Invalid argument
tar: virtualenv-1.4.6: Cannot change ownership to uid 1000, gid 1000: 
Invalid ar
gument
tar: Exiting with failure status due to previous errors
Error while expanding virtualenv-1.4.6.tar.gz

Original issue reported on code.google.com by iainsproat on 10 May 2010 at 12:06

[GoogleCodeExporter]

The above seem to be resolved when the patch in issue #9 is applied.  (I think 
the 
above was trying to deal with a nonexistent directory in it's confusion with 
paths 
containing spaces)  
http://code.google.com/p/freebase-gridworks/issues/detail?id=9

Original comment by iainsproat on 10 May 2010 at 12:33

[GoogleCodeExporter]

Fixed by the patch to issue #9

Original comment by stefano.mazzocchi@gmail.com on 10 May 2010 at 4:10

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by iainsproat on 11 May 2010 at 7:15

• Changed state: Verified

[GoogleCodeExporter]

Re-opening issue.  Seems it's transient and only occurs on the first 
'./gridworks test' 
run after initial checkout.

On running './gridworks test' again, the error disappears.

Original comment by iainsproat on 12 May 2010 at 10:25

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by stefano.mazzocchi@gmail.com on 12 May 2010 at 11:54

• Changed state: Started

[GoogleCodeExporter]

I can't repro on my machine, even with a fresh checkout. Can you repro after 
all the latest commits?

Original comment by stefano.mazzocchi@gmail.com on 13 May 2010 at 2:21

• Changed state: Accepted

[GoogleCodeExporter]

Still happening, unfortunately.
I tried running 'easy_install virtualenv' (in the offchance that might show a 
non-
gridworks related issue between virtualenv and my machine), but it works 
perfectly.

Original comment by iainsproat on 13 May 2010 at 8:03

[GoogleCodeExporter]

I've tried to reproduce this problem but I can't, so I suspect this has 
something to do with your machine (or with 
mine), so I'm considering this fixed until somebody else complains about it.

Original comment by stefano.mazzocchi@gmail.com on 1 Jun 2010 at 7:21

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by tfmorris on 18 Sep 2012 at 2:21

• Added labels: Milestone-2.0

[GoogleCodeExporter]

Original comment by tfmorris on 18 Sep 2012 at 2:49

• Added labels: Milestone-1.0
• Removed labels: Milestone-2.0