Issue metadata
Sign in to add a comment
|
"analyze" is flaky |
||||||||||||||||||||||||
Issue description"analyze" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is not infrastructure-related (e.g. flaky test), please add Sheriff-Chromium label and change issue status to Untriaged. When done, please remove the issue from Trooper Bug Queue by removing the Infra-Troopers label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyEgsSBUZsYWtlIgdhbmFseXplDA. This flaky test/step was previously tracked in issue 659032 .
,
Dec 16 2016
ERROR at build arg file (use "gn args <out_dir>" to edit):1:26: Build argument has no effect.
additional_target_cpus = [ "x86" ]
^-------
The variable "additional_target_cpus" was set as a build argument
but never appeared in a declare_args() block in any buildfile.
,
Dec 16 2016
Well, the log suggests to run gn args --list and I did. It recognizes additional_target_cpus as valid. The only thing that looks off to me is that it thinks the build directory is //out/Release, which is wrong. Maybe it needs to correctly set //out/Debug-iphonesimulator?
,
Dec 18 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by stip@chromium.org
, Dec 16 2016Owner: smut@chromium.org