gclient sync failing while compiling 122.0.6261.130 on macos

[richardmgoodin]

If the total change was just the depot_tools version in the CHROMIUM_BUILD_COMPATABILITY.txt file I tried the following:
1) Ran the automated build with a new download folder until failure
2) Updated CHROMIUM_BUILD_COMPATABILITY.txt file
3) Reran the same automate command line
4) Saw in the output that it picked up the depot_tools version
5) The build failed in a different location with a similar error

Did I miss something? Will this work with an automated build or do I need to revert to manual builds?

I tried backing up through the checked in versions of CHROMIUM_BUILD_COMPATABILITY.txt using git log but it is giving me very long commit hashes that don't work in CHROMIUM_BUILD_COMPATABILITY.txt.

[magreenblatt]

Create a private fork of CEF, commit the change to CHROMIUM_BUILD_COMPATABILITY.txt in the 6312 branch, and try a clean download/build of 6312 using your private fork.

[richardmgoodin]

Thanx Marshall,

But you have exceeded my knowledge of Git. What I did instead is checked out the version of depot_tools directly with the following calls:
git clone https://chromium.googlesource.com/chrom ... _tools.git
git checkout 4246ba023a

Then ran the automate script with the "--no-depot-tools-update" option.

python3 automate-git.py --download-dir=/home/goodin/CEF/download --build-target=cefsimple --x64-build --branch=6312 --no-debug-build --with-pgo-profiles --no-depot-tools-update

This worked, thanx again...

[lescobar]

I am running into the same issue in branch 5993 on Mac in x64 and arm64. I tried this branch a few months ago and it was working perfectly fine, but now when I try it does not work. I updated CHROMIUM_BUILD_COMPATABILITY.txt file but now I get a different error:

Traceback (most recent call last):
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/metrics.py", line 289, in print_notice_and_exit
yield
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/gclient.py", line 4431, in <module>
sys.exit(main(sys.argv[1:]))
^^^^^^^^^^^^^^^^^^
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/gclient.py", line 4417, in main
return dispatcher.execute(OptionParser(), argv)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/subcommand.py", line 254, in execute
return command(parser, args[1:])
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/gclient.py", line 3812, in CMDsync
ret = client.RunOnDeps('update', args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/gclient.py", line 2331, in RunOnDeps
work_queue.flush(revision_overrides,
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/gclient_utils.py", line 1026, in flush
reraise(e[0], e[1], e[2])
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/gclient_utils.py", line 53, in reraise
raise value
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/gclient_utils.py", line 1105, in run
self.item.run(*self.args, **self.kwargs)
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/gclient.py", line 2580, in run
self.DownloadGoogleStorage()
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/gclient.py", line 2699, in DownloadGoogleStorage
raise Exception(f'{code}: {err}')
Exception: 1: Traceback (most recent call last):
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/gsutil.py", line 325, in <module>
sys.exit(main())
^^^^^^
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/gsutil.py", line 321, in main
return run_gsutil(args.target, args.args, clean=args.clean)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/gsutil.py", line 229, in run_gsutil
gsutil_bin = ensure_gsutil(VERSION, target, clean)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/gsutil.py", line 133, in ensure_gsutil
shutil.move(download_dir, bin_dir)
File "/Users/lescobar/Library/Caches/.vpython-root/store/cpython+2gmfaoq44itr8h6pdvi4mdvnq8/contents/lib/python3.11/shutil.py", line 851, in move
raise Error("Destination path '%s' already exists" % real_dst)
shutil.Error: Destination path '/Volumes/SeagateDrive/lescobar_v118_mac_patch/maci/depot_tools/external_bin/gsutil/gsutil_4.68/d' already exists

[magreenblatt]

I am running into the same issue in branch 5993

Older branches are not supported. You can try updating the depot_tools version, but no guarantees that it will work.

[Phylanx]

Hi!

We're trying to build CEF version 122 for using it with JCEF.
Is there already a fix for 122, it still fails.

As far as I understand it there is a wrong depot_tool version in use, which version should it be?
Our parameters for syncing CEF are the following: --download-dir=J:\target --depot-tools-dir=J:\depot_tools --branch=6261 --checkout=c902316 --no-debug-build --no-release-build --no-distrib --no-build --force-clean

[Phylanx]

ah, sorry. didn't see the second page of the thread.
I'm trying the same fix as richardmgoodin:

git clone https://chromium.googlesource.com/chrom ... _tools.git
git checkout 4246ba023a

But additionally I'm doing an "update_depot_tools.bat" call in between, otherwise the "git.bat" command wouldn't be recognized as git.bat is created by update_depot_tools.bat:

Code: Select all

set PATH_DEPOT_TOOLS=J:\depot_tools
set DEPOT_TOOLS_GIT_REPOSITORY=https://chromium.googlesource.com/chromium/tools/depot_tools.git
set DEPOT_TOOLS_GIT_HASH=4246ba023a
...
...
...
mkdir %PATH_DEPOT_TOOLS%
cd /d %PATH_DEPOT_TOOLS%
cd ..
call git clone %DEPOT_TOOLS_GIT_REPOSITORY%
cd depot_tools
call update_depot_tools.bat
call git checkout %DEPOT_TOOLS_GIT_HASH%


[Phylanx]

Unfortunately the approach in my last post didn't work.
We really need a jcef build with the matching cef version also built.

As I see it we have the following options:

• Fork CEF and trial and error through multiple depot_tools versions and hope for the best
• Forget all work and fixes we already have done for 6261 (already upgraded jcef with downloaded CEF binaries) and upgrade to a new version (should be "130.1.9+gfc42567+chromium-130.0.6723.70")

Are there other easier options available that I'm missing?

Also as I see it we would have run in this problem even if we successfully upgraded to 6261 earlier because of the depot_tools changing.
Isn't that a problem in general for CEF builds?

We're upgrading the CEF/JCEF version only once a year (hopefully) and have to maintain our builds even longer because our customers (hospitals) need very long to install our upgrades.
How can we deal with that problem and be completely independent from the outside?
Is it possible to fork the whole CEF/JCEF/Chromium/depot_tools/... code? O_O

[ndesktop]

I don't know if that helps, I do have depot_tools for branc builds 5414, 5563, 6045, 6167, 6312, 6533 (and many more...) - all successfully building on Win10 x64 with VS2019 community edition.
For example, 6312 checkout I have is 4a9d989f.

If you want (although I don't recommend, since depot_tools contains executable files and there can be obvious trust issues, let's face it) I can upload on one of my development machines depot_tools.zip from what I have locally. Alternatively, I can give you a list of SHA-1 for whatever branch builds I have here, if it helps.

[Phylanx]

ok, i see. for now we'll try to jump directly to 6723 and hope for the best.
maybe you can give me the working git hash of depot_tools for 6261 just to check if I used the correct one?