Unable to build: fetch/gclient sync failing due to server error 400 when processing wayland-protocols

812 views
Skip to first unread message

Alesandro Ortiz

unread,
Apr 5, 2022, 4:09:26 PM4/5/22
to Chromium-dev
Hello,

I'm trying to build Chromium following these instructions, but keep running into the same error across different systems: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/linux/build_instructions.md

Any help would be appreciated, including providing Goma access as an external contributor/researcher. :)

I've tried in GCP Ubuntu 18.04 and 20.04, and AWS Ubuntu 18.04 with exactly the same results. Note that the attached and inline logs might be from different attempts, but they all behave the same, so you can ignore the different directory names.

I'm convinced this is a server or repo issue, but I've also tried updating git to the latest version from the developer and compiling the latest curl from source just in case, to no avail. I was able to perform all the steps a year or two ago on an AWS instance, so I'm not sure why doing it now is failing.

When running `fetch --nohooks --no-history chromium` (or `gclient sync --nohooks --nohistory`), I eventually run into the following error:

103>WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "clone" "--no-checkout" "--progress" "--verbose" "https://chromium.googlesource.com/external/anongit.freedesktop.org/git/wayland/wayland-protocols.git" "--template=/home/alesandro/chromium/src/third_party/wayland-protocols/_gclient_gittmp_src_oxkrv2x" "/home/alesandro/chromium/src/third_party/wayland-protocols/_gclient_src_lawi_yo8"' in /home/alesandro/chromium failed; will retry after a short nap...

The error above repeats 4 times because of four total attempts, and then it gives up with a bunch of additional errors presumably because that step failed (see attached output.log for the normal run).

When running fetch or gclient with --verbose, it shows that the request is failing due to:
[0:06:40] error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400
[0:06:40] fatal: the remote end hung up unexpectedly

The message above occurs while this is running:
git -c core.deltaBaseCacheLimit=2g clone --no-checkout --progress https://chromium.googlesource.com/external/anongit.freedesktop.org/git/wayland/wayland-protocols.git --template=/home/alesandro/chromium/src/third_party/wayland-protocols/_gclient_gittmp_srcks1c05mp /home/alesandro/chromium/src/third_party/wayland-protocols/_gclient_src_5dmo9d57

I've enabled git tracing but that doesn't provide much insight other than:

________ running 'git -c core.deltaBaseCacheLimit=2g clone --no-checkout --progress --verbose https://chromium.googlesource.com/external/anongit.freedesktop.org/git/wayland/wayland-protocols.git --template=/home/alesandro/chromium/src/third_party/wayland-protocols/_gclient_gittmp_src_oxkrv2x /home/alesandro/chromium/src/third_party/wayland-protocols/_gclient_src_lawi_yo8' in '/home/alesandro/chromium' attempt 4 / 4

[0:05:56] Cloning into '/home/alesandro/chromium/src/third_party/wayland-protocols/_gclient_src_lawi_yo8'...
[0:05:56] POST git-upload-pack (122 bytes)
[0:05:56] POST git-upload-pack (1018 bytes)
[0:05:57] error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400
[0:05:57] fatal: error reading section header 'shallow-info'
Traceback (most recent call last):
  File "/home/alesandro/depot_tools/gclient_scm.py", line 1116, in _Clone
    self._Run(clone_cmd, options, cwd=self._root_dir, retry=True,
  File "/home/alesandro/depot_tools/gclient_scm.py", line 1458, in _Run
    gclient_utils.CheckCallAndFilter(cmd, env=env, **kwargs)
  File "/home/alesandro/depot_tools/gclient_utils.py", line 682, in CheckCallAndFilter
    raise subprocess2.CalledProcessError(
subprocess2.CalledProcessError: Command 'git -c core.deltaBaseCacheLimit=2g clone --no-checkout --progress --verbose https://chromium.googlesource.com/external/anongit.freedesktop.org/git/wayland/wayland-protocols.git --template=/home/alesandro/chromium/src/third_party/wayland-protocols/_gclient_gittmp_src_oxkrv2x /home/alesandro/chromium/src/third_party/wayland-protocols/_gclient_src_lawi_yo8' returned non-zero exit status 128 in /home/alesandro/chromium
[0:06:01] _____ Conflicting directory found in /home/alesandro/chromium/src/third_party/wayland-protocols/src. Moving to /home/alesandro/chromium/_bad_scm/src/third_party/wayland-protocols/src3rotq9ef.

You can see the attached logs for the full non-verbose output, and the end of the verbose output, which provides a bit more context around the inline'd logs.

Again, any help would be appreciated to get past this gclient sync issue.

Regards,
Alesandro
output-full-noverbose.log
output-tail-verbose.log

Takuto Ikuta

unread,
Apr 5, 2022, 10:36:49 PM4/5/22
to ales...@alesandroortiz.com, Chromium-dev

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/16676b14-2da0-4a35-b695-3fdd3a71ce44n%40chromium.org.

Alesandro Ortiz

unread,
Apr 6, 2022, 1:49:31 PM4/6/22
to Chromium-dev
Hi All,

After sending the initial email, I found https://bugs.chromium.org/p/chromium/issues/detail?id=1226496 which described the same issue occurring back in July 2021.

Seems like the issue only occurs when using the --no-history flag. Without the flag, the fetch completed successfully.

I created a new crbug to track and (hopefully) fix the new occurrence of this issue with --no-history at https://bugs.chromium.org/p/chromium/issues/detail?id=1313310

Regards,
Alesandro

Lai Zhou

unread,
Apr 8, 2022, 1:15:58 PM4/8/22
to Chromium-dev, ales...@alesandroortiz.com
I had the same problem today. 
And I can clone https://chromium.googlesource.com/external/anongit.freedesktop.org/git/wayland/wayland-protocols.git independently.
Reply all
Reply to author
Forward
0 new messages