chromium/update.sh: don't use remote builders, lots of copying for work #48090
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using a machine setup for distributed builds, current script will download
the huge sources and copy them to a remote builder to perform some minor calculation
(perhaps computing the hash, not sure).
Using remote builders for this is rather unlikely to 'pay off' even with a very fast link,
since the size of the data copied is so large compared to what it's used for.
This tweaks the script to avoid using remote builders.
Hopefully this sounds good to everyone, but especially the person(s) who normally update our chrome bits :).
If not, whatever works best for that person is probably the way to go.
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)