[yocto] Random failure

Gary Thomas gary at mlbassoc.com
Tue Mar 21 06:08:39 PDT 2017


On 2017-03-16 13:08, Gary Thomas wrote:
> I've been running the same sequence many times today - basically
> updating a source file for a recipe, then rebuilding it.  Out of
> the 40+ times I've run it, I get these intermittent errors about
> 1 in 10 times.  Nothing changed except for one of the source files
> included in my recipe.  Here's the output:
>
> ===================================================================
> $ MACHINE=teton-p7621 bitbake production-tests && MACHINE=teton-p7621 bitbake package-index
> NOTE: Started PRServer with DBfile: /build/p7619_2016-02-23/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 44600, PID: 7064
> Loading cache: 100% |#############################################################################################|
> Time: 0:00:00
> Loaded 1717 entries from dependency cache.
> Parsing recipes: 100% |###########################################################################################|
> Time: 0:00:00
> Parsing of 1219 .bb files complete (1218 cached, 1 parsed). 1717 targets, 335 skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
> BB_VERSION        = "1.33.2"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "universal"
> TARGET_SYS        = "arm-amltd-linux-gnueabi"
> MACHINE           = "teton-p7621"
> DISTRO            = "amltd"
> DISTRO_VERSION    = "2.2+snapshot-20170316"
> TUNE_FEATURES     = "arm armv7ve vfp thumb neon callconvention-hard cortexa7"
> TARGET_FPU        = "hard"
> meta              = "master:b1f09df0f664052e39d939b759a63b05d767b8ec"
> meta-amltd        = "master:a57fa8ec07224f1d1d87e0357158bcbe7a4bc010"
> meta-teton-imx6-p761x = "master:a0b1a6c5e1f76ca74d93b26018eb0753a2306a29"
>
> Initialising tasks: 100% |########################################################################################|
> Time: 0:00:00
> Checking sstate mirror object availability: 100% |################################################################|
> Time: 0:00:00
> NOTE: Executing SetScene Tasks
> NOTE: Executing RunQueue Tasks
> ERROR: production-tests-1.0-r0 do_configure: Function failed: do_configure (log file is located at
> /build/p7619_2016-02-23/tmp/work/teton_p7621-amltd-linux-gnueabi/production-tests/1.0-r0/temp/log.do_configure.7131)
> ERROR: Logfile of failure stored in:
> /build/p7619_2016-02-23/tmp/work/teton_p7621-amltd-linux-gnueabi/production-tests/1.0-r0/temp/log.do_configure.7131
> Log data follows:
> | DEBUG: Executing python function sysroot_cleansstate
> | DEBUG: Removing manifest:
> /build/p7619_2016-02-23/tmp/sysroots-components/teton_p7621/production-tests/sysroot-providers/production-tests
> | DEBUG: Removing manifest: /build/p7619_2016-02-23/tmp/sysroots-components/teton_p7621/production-tests/sysroot-providers/
> | DEBUG: Python function sysroot_cleansstate finished
> | DEBUG: Executing shell function do_configure
> | find: ‘/build/p7619_2016-02-23/tmp/work/teton_p7621-amltd-linux-gnueabi/production-tests/1.0-r0/license-destdir’: No
> such file or directory
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_configure (log file is located at
> /build/p7619_2016-02-23/tmp/work/teton_p7621-amltd-linux-gnueabi/production-tests/1.0-r0/temp/log.do_configure.7131)
> ERROR: Task (/local/poky-cutting-edge/meta-teton-imx6-p761x/packages/misc/production-tests_1.0.bb:do_configure) failed
> with exit code '1'
> NOTE: Tasks Summary: Attempted 454 tasks of which 448 didn't need to be rerun and 1 failed.
>
> ===================================================================
>
> If I immediately rerun the same sequence, the error goes away.
>
> Any ideas what might be causing this?  It's more of an annoyance than
> anything else, but it also might point to a deeper problem?

I'm still seeing these failures a lot and it seems to be related to how
busy my system is doing other things.  For example, every day the 'locate'
database is rebuilt and while that happens, this error seems to be much
more likely.  It's also obvious that this is a timing related issue given
that it occurs randomly and non-repeatably.

It's a bit frustrating to have it happen so much but if there are any clues
I can gather, I'm happy to provide more information if it helps.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



More information about the yocto mailing list