Building chromium as external w. no perms

[Andrew Brown]

Hi,

I'm really sorry if this is something that's explained and documented somewhere obvious, but I've just git rebase-update'd my chromium checkout (& associated CL) and autoninja is no longer letting me compile. I've read back over the original "how to checkout and build" docs, but I can't spot anything substantial that's changed.

The exact problem is that I run autoninja -C out/Default chrome, but it immediately dies with credential errors complaining that I need to `siso login`. (This makes me suspicious, as I'm an external contributor who hasn't landed any CLs yet, so obviously I have no ability to run things remotely and autoninja/siso should just run locally, but whatever.)

If I do try to run `siso login`... the login flow errors out, with google's oauth service complaining that "This app tried to access sensitive info" and blocking the access. I've looked at the help page for autoninja, but nothing there strikes me as an obvious "it runs remotely by default, so please use this flag for a local compile".

Any advice as to which flags or configs I'm missing that would let me compile chromium locally, as I was doing this morning, would be hugely appreciated.'

Kind regards,

Andrew

[Greg Thompson]

Hi. Have a look at the recent announcement about Siso here: https://groups.google.com/a/chromium.org/g/chromium-dev/c/v-WOvWUtOpg/m/kj6bhVaCBQAJ. I haven't tried as an external contributor, but following the instructions for `siso login` may be all that you need to do.

--
You received this message because you are subscribed to the Google Groups "build" group.
To unsubscribe from this group and stop receiving emails from it, send an email to build+un...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/build/CAPiRGKPu-B2W%3DMnfiCSQg1josv8weRbL0Kg5i4VbMtXxABkHHg%40mail.gmail.com.

[Fumitoshi Ukai (鵜飼文敏)]

maybe https://crbug.com/429024909 and https://crbug.com/412384614 ?

try using `"siso_version": "latest"` in .gclient custom var  (fix for https://crbug.com/429024909 )

or `gcloud auth login --update-adc` (siso can use gcloud credentials too, so no need to `siso login`)

?

--

[Fumitoshi Ukai (鵜飼文敏)]

Did you run `gclient runhooks` ?

On Thu, Jul 3, 2025 at 9:22 AM Bryan Bernhart <bryan.b...@intel.com> wrote:

Using `"siso_version": "latest"` did nothing and  `gcloud auth login --update-adc` redirects to me a URL which cannot load (relies on localhost, and I must login from IT device).

I cannot build now without disabling siso.

Please advise.

[Fumitoshi Ukai (鵜飼文敏)]

ah, `--reapi_insecure` (or `export RBE_service_no_security=true`) might mitigate the issue?

[Fumitoshi Ukai (鵜飼文敏)]

hmm, how about `siso version` ?

On Thu, Jul 3, 2025 at 9:27 AM Bryan Bernhart <bryan.b...@intel.com> wrote:

Yes, I did run `gclient runhooks` and the error persists.

 0.02s Error: need to run `siso login`: failed to get token : exec: "gcloud": executable file not found in %PATH%

Bryan

[Bryan Bernhart]

Tried `set RBE_service_no_security=true` (using Windows CMD) and no change, same error.

`siso version` output is:

siso v1.3.4

CIPD package name: infra/build/siso/windows-amd64
CIPD instance ID:  QnzEeRv3oaRaIIlEp8nWvbrL-Sbys39XTT6o6m3Pt2QC
CIPD URL: https://chrome-infra-packages.appspot.com/p/infra/build/siso/windows-amd64/+/QnzEeRv3oaRaIIlEp8nWvbrL-Sbys39XTT6o6m3Pt2QC
https://chromium.googlesource.com/infra/infra/+/c46a6c9266d0685fa462694be456204ad243c030
c46a6c9266 siso: don't rebuild for last failure fix if manifest build failed.
 2025-07-01T07:00:00Z by uk...@google.com

Bryan

[Fumitoshi Ukai (鵜飼文敏)]

siso v1.3.4 is not the latest.

How did you set siso_version latest in .gclient ?

[Bryan Bernhart]

solutions = [
  {
    "name": "src",
    "url": "https://chromium.googlesource.com/chromium/src.git",
    "managed": False,
    "custom_deps": {},
    "custom_vars": {
      "checkout_clangd": True,
      "checkout_pgo_profiles": True,
    },
    "siso_version": "latest",
  },
]

Then I run `gclient sync` - is that correct?

[Fumitoshi Ukai (鵜飼文敏)]

no.

`"siso_version", "latest"` in "custom_vars" section. 

[Andrew Brown]

I dunno if my replies are going through, all I see is "deleted message" in the groups thread, but I still get emails, so fingers crossed.

On the off chance my replies are working and this is helpful, the command I had to run (in the root folder of my checkout) was gclient config --spec '{"siso_version": "latest"}'  , which then prompted me to `gn clean` and a couple of other things, but let me start compiling again without hassle.

I suspect what I was technically supposed to do was put "siso_version": "latest" into the root .gclient (outside the actual repo) as an item under the "custom_vars", but if it works, it works.

[Bryan Bernhart]

Yes, I missed "custom_vars" and now it works.

Ukai, strongly suggest we add a warning this var is now required.

Thanks for your help.

Bryan