First run of benchmark: https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20linux_benchmarks/1/overview, which took 57 mins without hitting any cache;
Second run of benchmark: https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20linux_benchmarks/2/overview, which took 10 mins.

The android_emulator_tests: https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20linux_android_emulator_tests/2/overview, which took 13 mins with cache hit.

In what situations will the build take 57 minutes?

In what situations will the build take 57 minutes?

Where we do not have a single cache hit:

num_records: 5510
stats: {
	name: "CompletionStatus"
	counts_by_value: {
		name: "STATUS_LOCAL_FALLBACK"
		count: 43
	}
	counts_by_value: {
		name: "STATUS_REMOTE_EXECUTION"
		count: 5467
	}
}

My question is in what situations can we expect to not have a single cache hit. Is this something that will happen on every commit? Once a day? Once a week?

My question is in what situations can we expect to not have a single cache hit. Is this something that will happen on every commit? Once a day? Once a week?

I expect this happens only the first time of the build, where the cache is empty (Run your builds and tests using the remote cache).

I expect this happens only the first time of the build, where the cache is empty (Run your builds and tests using the remote cache).

What does "the first time of the build" mean? The first time on any given commit? Or the first time with the repo?

I'm also confused by the documentation at that link. It says, "the cache is empty, so all actions are executed locally". That is very different from goma, which I believe uses the remote workers to run the compile commands even when there isn't a cache hit?

I expect this happens only the first time of the build, where the cache is empty (Run your builds and tests using the remote cache).

What does "the first time of the build" mean? The first time on any given commit? Or the first time with the repo?

I'm also confused by the documentation at that link. It says, "the cache is empty, so all actions are executed locally". That is very different from goma, which I believe uses the remote workers to run the compile commands even when there isn't a cache hit?

The first execution time with the task/builder, which should be the same with the repo.

I should have pointed out that the link focuses on using remote cache for local runs (the topic right after is Setting up remote execution) . Since we have set up remote execution, if no cache hit, it will try remote execution first. This is aligned with the stats: #45804 (comment)

I will monitor the coming builds to make sure things go well as expected. Landing now.