TL;DR; We're rolling out base_unittests_run using isolate on all the waterfalls on April 2.
After 12995019 lands April 2nd, base_unittests will be running in isolate mode for Linux and Windows. E.g. the test is running isolated in a temporary directory on the local VM.
This means that starting April 2nd: base_unitttests.isolate will need to be maintained. Any new test files that aren't listed in it will not be accessible to the test.
Plan
Once base_unittests is converted, if there are no major problems, on April 9th the CQ will begin to run base_unittests through Swarm for Linux and Windows. I don't expect there be be any noticeable change in the run times from this change.
Then all the remaining tests will be assimilated converted, which should finally complete our OKR of "running all tests in O(1)". M-A, Ben and I are working on making the .isolate format more human editable so it should eventually be self-serve.
How to try this out at home
http://chromium.org/developers/testing/isolated-testing/isolate-basics
If anyone has any problems or concerns with this plan, please let me know.
Thanks,
C#
Quick glossary
run_test_cases: Runs a single executable's test cases in parallel on a single machine, like sharding_supervisor. It assume the VM has more than one CPU.
isolate: runs a test outside of a checkout. This means listing all the run time dependencies,
http://www.chromium.org/developers/testing/isolated-testing
swarm: runs an executable on an arbitrary worker VM. Swarm knows about google-test so it can shards the work across multiple VMs to further reduce the end-to-end latency.
http://www.chromium.org/developers/testing/isolated-testing/swarm--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev