New issue
Advanced search Search tips

Issue 875358 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

nocturne-chrome-pfq fails to build Assistant

Project Member Reported by michae...@chromium.org, Aug 17

Issue description

The latest nocturne-chrome-pfq run (which began after the fix for  issue 874938  landed) failed.

It might just be a flake -- it looks like a git fetch failed -- but the path doesn't make sense to me:

> /b/swarming/w/ir/cache/cbuild/repository/.cache/distfiles/target-master/chrome-src-internal/src/chromeos/assistant/libassistant/src/third_party/android_ndk 

Are there supposed to be that many layers of "src"? There's a third_party/android_ndk in the root src directory.

Link to build: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8937975751246523808

Full failure:

[11421/45718] ACTION //chromeos/assistant/internal:build_libassistant(//build/toolchain/cros:target)
FAILED: obj/chromeos/assistant/internal/libassistant.so libassistant.so 
python ../../chromeos/assistant/internal/build_libassistant.py --root_out_dir . --target_out_dir obj/chromeos/assistant/internal
WARNING: subprocess '"git" "-c" "core.deltaBaseCacheLimit=2g" "fetch" "origin"' in /b/swarming/w/ir/cache/cbuild/repository/.cache/distfiles/target-master/chrome-src-internal/src/chromeos/assistant/libassistant/src/third_party/android_ndk failed; will retry after a short nap...
buildtools/clang_format/script (ERROR)
----------------------------------------
[0:00:01] Started.
----------------------------------------
Error: Command 'git rev-parse --verify FETCH_HEAD' returned non-zero exit status 128 in /b/swarming/w/ir/cache/cbuild/repository/.cache/distfiles/target-master/chrome-src-internal/src/chromeos/assistant/libassistant/src/buildtools/clang_format/script
fatal: Needed a single revision
Traceback (most recent call last):
  File "../../chromeos/assistant/internal/build_libassistant.py", line 163, in <module>
    sys.exit(main(sys.argv[1:]))
  File "../../chromeos/assistant/internal/build_libassistant.py", line 95, in main
    cwd=os.path.join(libassistant_standalone_path, 'src'))
  File "/usr/lib/python2.7/subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['gclient', 'sync', '-j32']' returned non-zero exit status 1

 
could be a flake.  now eve and eve-arcnext are also building assistant and they are green.

The build process for libassistant is a nested ninja build, if you are interested here is a doc that talks about how we settled with this approach.
https://docs.google.com/document/d/1XJEXL7qRHvTFbaQBy5aLLbmowZ-PP1mYPwiiy7IVDJQ/edit#heading=h.v8l0qcw3w8ht
Status: WontFix (was: Untriaged)
Looks like a flake.

Sign in to add a comment