ninja: error: unknown target 'video_decode_accelerator_perf_tests'

548 views
Skip to first unread message

Dev Wayne

unread,
Mar 19, 2019, 3:09:26 AM3/19/19
to Chromium OS Development
Hi all,
 
I am getting this error when I try to build custom chromeos-chrome in chroot :

chromeos-chrome-9999: ninja: Entering directory `c/Release'
chromeos-chrome-9999: ninja: error: unknown target 'video_decode_accelerator_perf_tests'
chromeos-chrome-9999:  * ERROR: chromeos-base/chromeos-chrome-9999::chromiumos failed (compile phase):
chromeos-chrome-9999:  *   (no error message)
chromeos-chrome-9999:  * 
chromeos-chrome-9999:  * Call stack:
chromeos-chrome-9999:  *     ebuild.sh, line  124:  Called src_compile
chromeos-chrome-9999:  *   environment, line 4395:  Called chrome_make 'chrome' 'capture_unittests' 'jpeg_decode_accelerator_unittest' 'jpeg_encode_accelerator_unittest' 'ozone_gl_unittests' 'sandbox_linux_unittests' 'video_decode_accelerator_perf_tests' 'video_decode_accelerator_tests' 'video_decode_accelerator_unittest' 'video_encode_accelerator_unittest' 'wayland_client_perftests' 'ppapi/examples/video_decode' 'bitmaptools' 'clear_system_cache' 'minidump_stackwalk' 'chromedriver' 'nacl_helper_bootstrap' 'nacl_helper'
chromeos-chrome-9999:  *   environment, line 1310:  Called die
chromeos-chrome-9999:  * The specific snippet of code:
chromeos-chrome-9999:  *       [[ "${ret}" -eq 0 ]] || die
chromeos-chrome-9999:  * 
chromeos-chrome-9999:  * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-chrome-9999::chromiumos'`,
chromeos-chrome-9999:  * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-chrome-9999::chromiumos'`.
chromeos-chrome-9999:  * The complete build log is located at '/build/amd64-generic/tmp/portage/logs/chromeos-base:chromeos-chrome-9999:20190319-065750.log'.
chromeos-chrome-9999:  * For convenience, a symlink to the build log is located at '/build/amd64-generic/tmp/portage/chromeos-base/chromeos-chrome-9999/temp/build.log'.
chromeos-chrome-9999:  * The ebuild environment file is located at '/build/amd64-generic/tmp/portage/chromeos-base/chromeos-chrome-9999/temp/environment'.
chromeos-chrome-9999:  * Working directory: '/home/dev01/chrome_root/src'
chromeos-chrome-9999:  * S: '/build/amd64-generic/tmp/portage/chromeos-base/chromeos-chrome-9999/work/chromeos-chrome-9999'
chromeos-chrome-9999: >>> Failed to emerge chromeos-base/chromeos-chrome-9999 for /build/amd64-generic/, Log file:
chromeos-chrome-9999: >>>  '/build/amd64-generic/tmp/portage/logs/chromeos-base:chromeos-chrome-9999:20190319-065750.log'
chromeos-chrome-9999: 
chromeos-chrome-9999:  * Messages for package chromeos-base/chromeos-chrome-9999 merged to /build/amd64-generic/:
chromeos-chrome-9999:  * Log file: /build/amd64-generic/tmp/portage/logs/chromeos-base:chromeos-chrome-9999:20190319-065750.log
chromeos-chrome-9999: 
chromeos-chrome-9999:  * If you want to develop or hack on the browser itself, you should follow the
chromeos-chrome-9999:  * simple chrome workflow instead of using emerge:
chromeos-chrome-9999:  * CHROME_ORIGIN VALUE is LOCAL_SOURCE
chromeos-chrome-9999:  * lld is forcibly disabled for non-chrome_internal builds; using gold instead (https://crbug.com/917504).
chromeos-chrome-9999:  * /home/dev01/chrome_root should be set here properly
chromeos-chrome-9999:  * ERROR: chromeos-base/chromeos-chrome-9999::chromiumos failed (compile phase):
chromeos-chrome-9999:  *   (no error message)
chromeos-chrome-9999:  * 
chromeos-chrome-9999:  * Call stack:
chromeos-chrome-9999:  *     ebuild.sh, line  124:  Called src_compile
chromeos-chrome-9999:  *   environment, line 4395:  Called chrome_make 'chrome' 'capture_unittests' 'jpeg_decode_accelerator_unittest' 'jpeg_encode_accelerator_unittest' 'ozone_gl_unittests' 'sandbox_linux_unittests' 'video_decode_accelerator_perf_tests' 'video_decode_accelerator_tests' 'video_decode_accelerator_unittest' 'video_encode_accelerator_unittest' 'wayland_client_perftests' 'ppapi/examples/video_decode' 'bitmaptools' 'clear_system_cache' 'minidump_stackwalk' 'chromedriver' 'nacl_helper_bootstrap' 'nacl_helper'
chromeos-chrome-9999:  *   environment, line 1310:  Called die
chromeos-chrome-9999:  * The specific snippet of code:
chromeos-chrome-9999:  *       [[ "${ret}" -eq 0 ]] || die
chromeos-chrome-9999:  * 
chromeos-chrome-9999:  * If you need support, post the output of `emerge --info '=chromeos-base/chromeos-chrome-9999::chromiumos'`,
chromeos-chrome-9999:  * the complete build log and the output of `emerge -pqv '=chromeos-base/chromeos-chrome-9999::chromiumos'`.
chromeos-chrome-9999:  * The complete build log is located at '/build/amd64-generic/tmp/portage/logs/chromeos-base:chromeos-chrome-9999:20190319-065750.log'.
chromeos-chrome-9999:  * For convenience, a symlink to the build log is located at '/build/amd64-generic/tmp/portage/chromeos-base/chromeos-chrome-9999/temp/build.log'.
chromeos-chrome-9999:  * The ebuild environment file is located at '/build/amd64-generic/tmp/portage/chromeos-base/chromeos-chrome-9999/temp/environment'.
chromeos-chrome-9999:  * Working directory: '/home/dev01/chrome_root/src'
chromeos-chrome-9999:  * S: '/build/amd64-generic/tmp/portage/chromeos-base/chromeos-chrome-9999/work/chromeos-chrome-9999'
=== Complete: job chromeos-chrome-9999 (0m14.2s) ===
Failed chromeos-base/chromeos-chrome-9999 (in 0m14.2s). Your build has failed.
Pending 12/842, [Time 15:58:04 | Elapsed 17m11.4s | Load 3.53 5.92 4.95]
ERROR   : Tue Mar 19 15:58:05 KST 2019
ERROR   :  PGID  PPID   PID     ELAPSED     TIME %CPU COMMAND
ERROR   :     8     4     8    01:23:45 00:00:00  0.0 -bash
ERROR   :  4585     8  4585       19:31 00:00:00  0.0  \_ /bin/bash ./build_packages --board=amd64-generic
ERROR   :  4585  4585 15382       00:00 00:00:00  0.0      \_ /bin/bash ./build_packages --board=amd64-generic
ERROR   :  4585 15382 15383       00:00 00:00:00  0.0          \_ ps f -o pgid,ppid,pid,etime,cputime,%cpu,command
ERROR   : Arguments of 4585: ./build_packages '--board=amd64-generic'
ERROR   : Backtrace:  (most recent call is last)
ERROR   :  build_packages:365:main(), called: die_err_trap  
ERROR   : 
ERROR   : Command failed:
ERROR   :   Command '( if [[ "${FLAGS_run_goma}" -eq "${FLAGS_TRUE}" ]]; then
ERROR   :     info "Starting goma compiler_proxy."; goma_ctl="${GOMA_DIR:-${HOME}/goma}/goma_ctl.py"; "${goma_ctl}" restart; trap "'${goma_ctl}' stop" EXIT;
ERROR   : fi; GOMA_WRAPPER=(); if [[ "${FLAGS_build_all_with_goma}" -eq "${FLAGS_TRUE}" ]]; then
ERROR   :     warn "The build_all_with_goma feature is still under development."; warn "This feature is experimental and may potentially break your build."; GOMA_WRAPPER=("${GOMA_DIR:-${HOME}/goma}/goma-wrapper" -j600 -l100);
ERROR   : fi; sudo -E "${GOMA_WRAPPER[@]}" "${EMERGE_CMD[@]}" "${EMERGE_FLAGS[@]}" "${PACKAGES[@]}" )' exited with nonzero code: 1

I am unable to find anything on how to solve this.
Can anyone please guide me on how to walk around this issue? 

Thanks 

David Staessens

unread,
Mar 26, 2019, 4:59:15 PM3/26/19
to Chromium OS Development

The 'video_decode_accelerator_perf_tests' target was added to chromeos-chrome in http://crrev.com/c/1475311. The tests itself were added earlier to Chrome in http://crrev.com/c/1429306. It looks to me like your local Chrome checkout might be out of date.
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages