Fetch Chromium Keeps failing

1,894 views
Skip to first unread message

Lingeshwaran Palaniappan

unread,
Jun 20, 2013, 2:42:50 PM6/20/13
to Chromium-dev
Hi,
I am doing a fresh checkout using the git checkout instruction and fetch chromium keeps failing with the error that it got no output for x seconds and killing the process.

(I wiped my exact error but I am sure I will get it again and paste the exact text if needed)

I looked at .gclient and it looks like it is downloading all the files. Would it be OK to change the .gclient to exclude some of the big directories(like layouttests)? 

What I am thinking is, do a fetch chromium, when it fails edit the .gclient's custom deps and run gclient sync(on the unfinished checkout). Would that work?

Any other ideas?

Thanks!


Lingeshwaran Palaniappan

unread,
Jun 20, 2013, 2:44:15 PM6/20/13
to Chromium-dev
Here is the latest error(although this is different from the process killed error I mentioned earlier)
1>error: RPC failed; result=18, HTTP code = 200
1>fatal: The remote end hung up unexpectedly
1>fatal: early EOF
1>fatal: index-pack failed
Error: Command git clone --progress -b master https://chromium.googlesource.com/chromium/src.git /cygdrive/d/src returned non-zero exit status 128 in /cygdrive/d
Traceback (most recent call last):
  File "/cygdrive/d/depot_tools/fetch.py", line 278, in <module>
    sys.exit(main())
  File "/cygdrive/d/depot_tools/fetch.py", line 274, in main
    return run(dryrun, spec, root)
  File "/cygdrive/d/depot_tools/fetch.py", line 268, in run
    return checkout.init()
  File "/cygdrive/d/depot_tools/fetch.py", line 149, in init
    super(GclientGitSvnCheckout, self).init()
  File "/cygdrive/d/depot_tools/fetch.py", line 117, in init
    self.run_gclient('sync')
  File "/cygdrive/d/depot_tools/fetch.py", line 75, in run_gclient
    return self.run(cmd_prefix + cmd, **kwargs)
  File "/cygdrive/d/depot_tools/fetch.py", line 65, in run
    return subprocess.check_call(cmd, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 511, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '('gclient', 'sync')' returned non-zero exit status 1

Scott Graham

unread,
Jun 20, 2013, 3:16:59 PM6/20/13
to Lingeshwaran Palaniappan, Chromium-dev
It's very difficult to get it to complete on Windows.

You might try https://codereview.chromium.org/16004008/ or use "fetch -n" and then run the commands it emits manually.


--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
 
 
 

Nico Weber

unread,
Jun 20, 2013, 3:40:28 PM6/20/13
to Scott Graham, Lingeshwaran Palaniappan, Chromium-dev
For what it's worth, I tried `fetch chromium` four times on a Windows box on Chromium and it never succeeded for me. I ended up using the old git method (manually clone the chromium git repo, then use `gclient init` in svn mode to pull deps), which worked fine.

Lingeshwaran Palaniappan

unread,
Jun 20, 2013, 3:51:15 PM6/20/13
to Nico Weber, Scott Graham, Chromium-dev
Nico what are the commands to do it manually?

Scott - when I type in the -n option it is not recognized.(I typed in fetch -n chromium, The error is index out of range)

Thanks!

Scott Graham

unread,
Jun 20, 2013, 3:52:47 PM6/20/13
to Lingeshwaran Palaniappan, Nico Weber, Chromium-dev
On Thu, Jun 20, 2013 at 12:51 PM, Lingeshwaran Palaniappan <lipa...@google.com> wrote:
Nico what are the commands to do it manually?

Scott - when I type in the -n option it is not recognized.(I typed in fetch -n chromium, The error is index out of range)

Perhaps make sure your depot_tools is properly up to date? I get this:

D:\src\cr4>fetch -n chromium
Running: 'D:\src\depot_tools\svn_bin\svn.exe' ls --non-interactive svn://svn.chromium.org/chrome
Running: 'D:\src\depot_tools\git-1.8.0_bin\bin\git.exe' config --global core.deltaBaseCacheLimit 1G
Running: 'D:\src\depot_tools\python_bin\python.exe' 'D:\src\depot_tools\gclient.py' config --spec "solutions = [{u'managed': True, u'name': u'src', u'url': u'https://chromium.googlesource.com/chromium/src.git', u'custom_deps': {}, u'deps_file': u'.DEPS.git', u'safesync_url': u''}]"
Running: 'D:\src\depot_tools\python_bin\python.exe' 'D:\src\depot_tools\gclient.py' sync
cd D:\src\cr4\src
Running: 'D:\src\depot_tools\git-1.8.0_bin\bin\git.exe' submodule foreach 'git config -f $toplevel/.git/config submodule.$name.ignore all'
Running: 'D:\src\depot_tools\git-1.8.0_bin\bin\git.exe' config diff.ignoreSubmodules all
cd D:\src\cr4\src
Running: 'D:\src\depot_tools\git-1.8.0_bin\bin\git.exe' svn init --prefix=origin/ -T trunk/src svn://svn.chromium.org/chrome
Running: 'D:\src\depot_tools\git-1.8.0_bin\bin\git.exe' config --replace svn-remote.svn.fetch trunk/src:refs/remotes/origin/git-svn
Running: 'D:\src\depot_tools\git-1.8.0_bin\bin\git.exe' svn fetch

Lingeshwaran Palaniappan

unread,
Jun 20, 2013, 3:55:06 PM6/20/13
to Scott Graham, Nico Weber, Chromium-dev
Scott - you seem to be using the command prompt. I am running fetch chromium under cygwin. Is that right?

Scott Graham

unread,
Jun 20, 2013, 3:59:30 PM6/20/13
to Lingeshwaran Palaniappan, Nico Weber, Chromium-dev
I don't see any reason why cygwin wouldn't work (depot_tools/fetch looks reasonable?), but yes, I'm using cmd and depot_tools\fetch.bat.

Lingeshwaran Palaniappan

unread,
Jun 20, 2013, 4:00:04 PM6/20/13
to Scott Graham, Nico Weber, Chromium-dev
I got the depot_tools issues resolved(it was actually up to date but I had a left over folder by the name src from previous attempts which was the cause of the error)

fetch -n works now. I am doing the commands manually. 

Thanks Scott. Fingers crossed!

Stephen Chenney

unread,
Jun 20, 2013, 4:16:36 PM6/20/13
to lipa...@google.com, Scott Graham, Nico Weber, Chromium-dev
The only way I made it succeed last week was to edit depot_tools/gclient_scm.py and change lines 123 and 124:

nag_timer = 60
nag_max = 100

Then do each command individually (although it also works, I think, if you do it all in one shot).

You probably want to change it back again when you're done. There are a couple of errors you can ignore - they happen after git steps to rebuild indexes, or something like that. Don't be scared if the whole thing seems to hang for a long time - it is doing something.

Cheers,
Stephen.
Reply all
Reply to author
Forward
0 new messages