Bug 8043 - perf build failure
Summary: perf build failure
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: kernel (show other bugs)
Version: 1.9
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks: 8176
  Show dependency tree
 
Reported: 2015-07-23 20:36 UTC by Ross Burton
Modified: 2015-08-17 19:00 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2015-07-23 20:36:20 UTC
With 4.1.2 kernel there are two build failures that have repeated (but not always) on the autobuilder.

eg https://autobuilder.yoctoproject.org/main/builders/nightly-world/builds/405/steps/BuildImages/logs/stdio

| make[3]: *** No rule to make target '.../work/qemux86-poky-linux/perf/1.0-r9/perf-1.0/util/parse-events-flex.o', needed by '.../work/qemux86-poky-linux/perf/1.0-r9/perf-1.0/util/libperf-in.o'.  Stop.

(odd)

|   LD       .../work/qemux86-poky-linux/perf/1.0-r9/perf-1.0/perf-in.o
| .../work/qemux86-poky-linux/perf/1.0-r9/perf-1.0/builtin-probe.o: file not recognized: File truncated
| .../work-shared/qemux86/kernel-source/tools/build/Makefile.build:112: recipe for target '.../work/qemux86-poky-linux/perf/1.0-r9/perf-1.0/perf-in.o' failed

(build race?)
Comment 1 Bruce Ashfield 2015-07-24 19:51:57 UTC
ross: how often is this happening ? Would it be possible to do some runs with parallel make disabled ? I'd like to determine if this is a task race, or a Makefile dependency race.
Comment 2 Ross Burton 2015-07-24 20:26:42 UTC
Occasionally, I've seen it on the AB twice and a few times locally.  If I can replicate here I'll disable parallel builds.
Comment 3 Ross Burton 2015-07-24 20:32:52 UTC
Happened again in the world build:
https://autobuilder.yoctoproject.org/main/builders/nightly-world/builds/409/steps/BuildImages/logs/stdio

(I also note that it found lzma in that run)