Chromium Dev Build Packages Fail

[Scott Conover]

I was going through the typical Chromium OS build yesterday as per the dev guide, and when I was building my packages, I ran into this error:

---

userfeedback-0.0.1-r97:     str(portage.checksum.perform_md5(pkg_path)) + "\n"))
userfeedback-0.0.1-r97:   File "/usr/lib64/portage/pym/portage/checksum.py", line 190, in perform_md5
userfeedback-0.0.1-r97:     return perform_checksum(x, "MD5", calc_prelink)[0]
userfeedback-0.0.1-r97:   File "/usr/lib64/portage/pym/portage/checksum.py", line 392, in perform_checksum
userfeedback-0.0.1-r97:     myhash, mysize = hashfunc_map[hashname](myfilename)
userfeedback-0.0.1-r97:   File "/usr/lib64/portage/pym/portage/checksum.py", line 53, in __call__
userfeedback-0.0.1-r97:     with _open_file(filename) as f:
userfeedback-0.0.1-r97:   File "/usr/lib64/portage/pym/portage/checksum.py", line 32, in _open_file
userfeedback-0.0.1-r97:     raise portage.exception.FileNotFound(filename)
userfeedback-0.0.1-r97: FileNotFound: /build/x86-generic/packages/chromeos-base/userfeedback-0.0.1-r97.tbz2
=== Complete: job userfeedback-0.0.1-r97 (0m0.2s) ===
Failed chromeos-base/userfeedback-0.0.1-r97 (in 0m0.2s). Your build has failed.
Pending 34/100, [Time 103m19.8s Load 0.68 0.61 0.56]
Packages failed:
    net-wireless/bluez-5.4-r14
    chromeos-base/userfeedback-0.0.1-r97
    app-misc/utouch-evemu-1.0.5-r9
ERROR   : script called: ./build_packages '--board=x86-generic'
ERROR   : Backtrace:  (most recent call is last)
ERROR   :   file build_packages, line 260, called: die_err_trap '[[ $# -eq 0 ]]' '1'
ERROR   :
ERROR   : Command failed:
ERROR   :   Command '[[ $# -eq 0 ]]' exited with nonzero code: 1

---

I ran the build again in case it was a fluke, and it came up again. The board is x86-generic, I have a cros-workon with 3.10 for some minor things, but I have no special packages. I repo synced yesterday before I started the build, so I do not think the repo is out of date.

I had to step away from Chromium for a few weeks, so I just might be rusty. Any tips?

[Mukesh Agrawal]

This looks a bit like crbug.com/348805, which is an infrastructure issue. +davidjames might be able to offer advice about a work-around.

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[Mike Frysinger]

there seems to be a race condition in the package code atm coupled with some bugs in GS which impact uploaded binpkgs.  you should be able to work around it by running build_packages with --nousepkg and it'll build things locally for that run.

-mike

--

[Scott Conover]

Mike,

I originally ran the command with ./build_packages --nousepkg --board=${BOARD}, and it failed. I should have mentioned that - for a few months now, every time I repo sync, I run the commands to bootstrap locally (--nousepkg) before I start churning out image variations with --usepkg.

-Scott

[Mike Frysinger]

hmm, that is funky

if you run `emerge-$BOARD userfeedback`, does it work ?

-mike

[Scott Conover]

Comes out clean:

---------------

 sudo emerge-$BOARD userfeedback
Calculating dependencies... done!

>>> Emerging (1 of 1) chromeos-base/userfeedback-0.0.1-r97 from chromiumos for /build/x86-generic/
 * Running stacked hooks for pre_pkg_setup
 *    sysroot_build_bin_dir ...                                           [ ok ]
 * Running stacked hooks for pre_src_unpack
 *    python_multilib_setup ...                                           [ ok ]
>>> Unpacking source...
Cloning into '/build/x86-generic/tmp/portage/chromeos-base/userfeedback-0.0.1-r97/work/userfeedback-0.0.1'...
done.
Checking connectivity... done
>>> Source unpacked in /build/x86-generic/tmp/portage/chromeos-base/userfeedback-0.0.1-r97/work
>>> Preparing source in /build/x86-generic/tmp/portage/chromeos-base/userfeedback-0.0.1-r97/work/userfeedback-0.0.1 ...
>>> Source prepared.
>>> Configuring source in /build/x86-generic/tmp/portage/chromeos-base/userfeedback-0.0.1-r97/work/userfeedback-0.0.1 ...
>>> Source configured.
>>> Compiling source in /build/x86-generic/tmp/portage/chromeos-base/userfeedback-0.0.1-r97/work/userfeedback-0.0.1 ...
>>> Source compiled.
>>> Test phase [not enabled]: chromeos-base/userfeedback-0.0.1-r97

>>> Install userfeedback-0.0.1-r97 into /build/x86-generic/tmp/portage/chromeos-base/userfeedback-0.0.1-r97/image/ category chromeos-base
>>> Completed installing userfeedback-0.0.1-r97 into /build/x86-generic/tmp/portage/chromeos-base/userfeedback-0.0.1-r97/image/

 * Removing /usr/lib*/*.la
 * Removing /etc/init.d
 * Removing /etc/conf.d
 * Removing /etc/logrotate.d
 * Removing /etc/sandbox.d
 * Removing /usr/share/bash-completion
>>> Done.

>>> Installing (1 of 1) chromeos-base/userfeedback-0.0.1-r97 to /build/x86-generic/
 * Removing /usr/lib*/*.la
 * Removing /etc/init.d
 * Removing /etc/conf.d
 * Removing /etc/logrotate.d
 * Removing /etc/sandbox.d
 * Removing /usr/share/bash-completion
 * Removing /usr/share/man
 * Removing /usr/share/info
 * Removing /usr/share/doc
 * Running stacked hooks for pre_pkg_preinst
 *    wrap_old_config_scripts ...                                         [ ok ]
>>> Auto-cleaning packages...

>>> Using system located in ROOT tree /build/x86-generic/

>>> No outdated packages were found on your system.

--------------

-Scott

[Scott Conover]

Emerging userfeedback did the trick, although it took longer than normal to complete the bootstrap. I'll have to remember to emerge the failed package(s) manually if I come across this error again.

-----------

Completed chromeos-base/autotest-all-0.0.1-r19 (in 0m6.7s)
Pending 0/35, [Time 325m51.6s Load 0.69 2.12 2.47]
Merge complete
Done
Builds complete
INFO    : Elapsed time (build_packages): 326m12s
Done

-----------

Its interesting that the error occurred originally during a bootstrap build, but I have no real idea as to the cause.

-Scott

[Mike Frysinger]

the log should show how long each individual package took.  can you scroll up and see which one took forever ?  most likely it was chrome ...

-mike

[Scott Conover]

Mike,

Normally I glance at the history or just pipe it if I really want to know. While building, it was still on chrome, but I am not entirely sure if it was the longest. Where can I find build logs within my source?

-Scott

[Mike Frysinger]

the individual logs don't include timestamps, only the summary from build_packages does

-mike