enable_nacl = false breaks isolated testing on Chrome OS |
|||
Issue descriptionWith the following args.gn, isolated CrOS fails: target_os = "chromeos" is_debug = false is_component_build = true enable_nacl = false use_goma = true $ ninja -C out_cros/Release chrome browser_tests $ python tools/swarming_client/isolate.py check -i out_cros/Release/browser_tests.isolate -s out_cros/Release/browser_tests.isolated Failed to find an input file: /foo/src/out_cros/Release/chromevox_test_data/ is not a directory but ends with "/" -> returned 1 Execution failure: A .isolate file is required. indeed, chromevox_test_data doesn't exist anywhere in out_cros/Release when building browser_tests with enable_nacl = false. This works with enable_nacl = true though.
,
Sep 4 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 5 2017
I wonder if this is still a problem (?)
,
Oct 25 2017
|
|||
►
Sign in to add a comment |
|||
Comment 1 by benhenry@chromium.org
, Sep 1 2016