Version: tot, r427453
What steps will reproduce the problem?
(1) $ gn gen out/Release --args='is_debug=false use_goma=true target_os="chromeos" is_component_build=true remove_webcore_debug_symbols=true'
(2) $ ninja -C out/Release -j1000 unit_tests
(3) $ ninja -C out/Release -j1000 unittests
What is the expected output?
2) succeeds but 3) fails.
What do you see instead?
Both unit_tests and unittests are valid ninja targets, and because of this, both succeed.
unit_tests are Chrome's unit tests of course, and unittests are for WASM probably?
Please use labels and text to provide additional information.
What about using a more descriptive target name like 'wasm_unittests' for the latter? It took me 10 minutes or so to figure out why 'ninja unittests' did not rebuild my Chrome tests...
I only tested with target_os=chromeos, but Windows, Mac, and Linux builds likely have the same issue.
Comment 1 by yusukes@chromium.org
, Oct 25 2016