Bug 12443

Summary: [Test Case 312,313] Bitbake failed after using yocto-kernel add patch
Product: [Build System, Metadata & Runtime] OE-Core Reporter: yeoh ee peng <ee.peng.yeoh>
Component: Scripts and ToolsAssignee: Stephano Cetola <stephano>
Status: RESOLVED WONTFIX QA Contact:
Severity: major    
Priority: Undecided CC: richard.purdie, ross.burton
Version: 2.4.1   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description yeoh ee peng 2017-12-21 07:39:56 UTC
Steps to reproduce error:
pokyuser@029f91c4fdce:/workdir/build$ yocto-kernel patch add myqemuarm Yocto-testmod.patch
Added patches:
        Yocto-testmod.patch
pokyuser@029f91c4fdce:/workdir/build$ yocto-kernel patch list myqemuarm
The current set of machine-specific patches for myqemuarm is:
        1) Yocto-testmod.patch
 
pokyuser@029f91c4fdce:/workdir/build$ yocto-kernel config list myqemuarm
The current set of machine-specific kernel config items for myqemuarm is:
        1) CONFIG_MISC_DEVICES=y
        2) CONFIG_YOCTO_TESTMOD=y
        3) CONFIG_FTRACE_SYSCALLS=y
        4) CONFIG_SCHED_TRACER=y
        5) CONFIG_IRQSOFF_TRACER=y
        6) CONFIG_PREEMPT_TRACER=y
 
pokyuser@029f91c4fdce:/workdir/build$ bitbake core-image-sato
 
ERROR: linux-yocto-4.12.14+gitAUTOINC+e3c9041f48_4226b065fc-r0.8 do_kernel_metadata: Could not locate BSP definition for myqemuarm/standard and no defconfig was provided
ERROR: linux-yocto-4.12.14+gitAUTOINC+e3c9041f48_4226b065fc-r0.8 do_patch: Could not apply patches for myqemuarm.
ERROR: linux-yocto-4.12.14+gitAUTOINC+e3c9041f48_4226b065fc-r0.8 do_patch: Patch failures can be resolved in the linux source directory /workdir/build/tmp/work-shared/myqemuarm/kernel-source)
ERROR: linux-yocto-4.12.14+gitAUTOINC+e3c9041f48_4226b065fc-r0.8 do_patch: Function failed: do_patch (log file is located at /workdir/build/tmp/work/myqemuarm-poky-linux-gnueabi/linux-yocto/4.12.14+gitAUTOINC+e3c9041f48_4226b065fc-r0.8/temp/log.do_patch.20311)
ERROR: Logfile of failure stored in: /workdir/build/tmp/work/myqemuarm-poky-linux-gnueabi/linux-yocto/4.12.14+gitAUTOINC+e3c9041f48_4226b065fc-r0.8/temp/log.do_patch.20311
 
Log data follows:
| DEBUG: Executing python function extend_recipe_sysroot
| NOTE: Direct dependencies are ['/workdir/poky/meta/recipes-devtools/quilt/quilt-native_0.65.bb:do_populate_sysroot', '/workdir/poky/meta/recipes-kernel/kern-tools/kern-tools-native_git.bb:do_populate_sysroot']
| NOTE: Installed into sysroot: []
| NOTE: Skipping as already exists in sysroot: ['quilt-native', 'kern-tools-native']
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing shell function do_patch
| (1/1) Yocto-testmod.patch
| [INFO]: check of .kernel-meta//patches//./Yocto-testmod.patch with "git am" did not pass, trying reduced context.
| [INFO]: Context reduced git-am of .kernel-meta//patches//./Yocto-testmod.patch with "git am" did not work, trying "apply".
| error: patch failed: drivers/misc/Kconfig:392
| error: drivers/misc/Kconfig: patch does not apply
| Context reduced to (1/1) to apply fragment at 35
| [ERROR]: Application of .kernel-meta//patches//./Yocto-testmod.patch failed.
|          Patch needs to be refreshed. Sample resolution script:
|              .git/rebase-apply/resolve_rejects
| ERROR: Could not apply patches for myqemuarm.
| ERROR: Patch failures can be resolved in the linux source directory /workdir/build/tmp/work-shared/myqemuarm/kernel-source)
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_patch (log file is located at /workdir/build/tmp/work/myqemuarm-poky-linux-gnueabi/linux-yocto/4.12.14+gitAUTOINC+e3c9041f48_4226b065fc-r0.8/temp/log.do_patch.20311)
ERROR: Task (/workdir/poky/meta/recipes-kernel/linux/linux-yocto_4.12.bb:do_patch) failed with exit code '1'
Comment 1 Richard Purdie 2017-12-21 16:01:33 UTC
At this point we don't have the resources to maintain this, we're going to mark this as WONTFIX since we removed the functionality in master. We should continue to test but we'll only fix issues which are easy to fix or where there is significant user impact.