Make "repo forall" more resilient to missing projects, repo synced to older manifest, etc.

[GoogleCodeExporter]

Reported by Andrew D. Stadler (Google) <stadler@android.com> on Mon Jul 13 
22:34:38 PDT 2009
Source: JIRA REPO-43

Forwarded conversation
Subject: can't obtain weekly report while synced to an older build
------------------------
Original report:

$ repo forall -pc git log --all --author=stadler --since=8.days.ago
Traceback (most recent call last):
 File "/Volumes/src/repo/master/.repo/repo/main.py", line 235, in <module>
   _Main(sys.argv[1:])
 File "/Volumes/src/repo/master/.repo/repo/main.py", line 217, in _Main
   repo._Run(argv)
 File "/Volumes/src/repo/master/.repo/repo/main.py", line 123, in _Run
   cmd.Execute(copts, cargs)
 File "/Volumes/src/repo/master/.repo/repo/subcmds/forall.py", line
187, in Execute
   stderr = stderr)
 File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/
subprocess.py",
line 593, in __init__
   errread, errwrite)
 File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/
subprocess.py",
line 1079, in _execute_child
   raise child_exception
OSError: [Errno 2] No such file or directory:
'/Volumes/src/repo/master/external/bluetooth/bluez'

Note:  This is happening while I am synced to an earlier build # (the build
was broken), which is probably related.

The build has turned green since, so I'm trying an init to default.xml, repo
sync, and repeat the command.  But it seems like getting weekly stats should
work even if one is temporarily parked on an older build.

Should I file a bug?  Workaround?

--Andy

p.s.  Confirmed:  after repo sync, it works properly.

----------
Response from Shawn:

Feature request please.  We should have been able to execute this
against a bare repository and not a working directory (e.g. with a
--bare flag) and we should have been able to continue (but with an
error message to stderr) even though one project doesn't exist.  In a
case of "what have I done the past 8 days" skipping a project you do
not have (but with an one line error/warning message) is probably OK,
you don't have it so you didn't work in it.  In other cases it may be
important, e.g. grep'ing for something about bluez and you don't have
bluez is a certain problem.  :-)

Original issue reported on code.google.com by code-rev...@gtempaccount.com on 24 Sep 2009 at 9:10

[GoogleCodeExporter]

Comment by Shawn Pearce <sop@google.com> on Sat Aug 22 18:51:29 PDT 2009

Fixed by change I64f97eb315f379ab2c51fc53d24ed340b3d09250

Original comment by code-rev...@gtempaccount.com on 24 Sep 2009 at 9:11

[GoogleCodeExporter]

Update by Shawn Pearce <sop@google.com> on Sat Aug 22 18:51:29 PDT 2009

Fixed in version 1.7.0.

Original comment by code-rev...@gtempaccount.com on 24 Sep 2009 at 9:11

• Changed state: Fixed