yocto-check-layer-wrapper ../meta-qcom --no-auto-dependency

Running '. ./init-build-env; yocto-check-layer-wrapper ../meta-qcom --no-auto-dependency' with output to /srv/pokybuild/yocto-worker/check-layer-nightly/build/build/command-10-cmds.log in /srv/pokybuild/yocto-worker/check-layer-nightly/build/build
Poky - The Yocto Project testing distribution
You had no conf/local.conf file. This configuration file has therefore been
created for you from /srv/pokybuild/yocto-worker/check-layer-nightly/build/layers/openembedded-core/meta/conf/templates/default/local.conf.sample
You may wish to edit it to, for example, select a different MACHINE (target
hardware).

You had no conf/bblayers.conf file. This configuration file has therefore been
created for you from /srv/pokybuild/yocto-worker/check-layer-nightly/build/layers/openembedded-core/meta/conf/templates/default/bblayers.conf.sample
To add additional metadata layers into your configuration please add entries
to conf/bblayers.conf.

The Yocto Project has extensive documentation about OE including a reference
manual which can be found at:
    https://docs.yoctoproject.org

For more information about OpenEmbedded see the website:
    https://www.openembedded.org/

This is the default build configuration for the openembedded-core layer.

### Shell environment set up for builds. ###

You can now run 'bitbake <target>'

Common targets are:
    core-image-minimal
    core-image-full-cmdline
    core-image-sato
    core-image-weston
    meta-toolchain
    meta-ide-support

You can also run generated qemu images with a command like 'runqemu qemux86-64'.

Other commonly useful commands are:
 - 'devtool' and 'recipetool' handle common recipe tasks
 - 'bitbake-layers' handles common layer tasks
 - 'oe-pkgdata-util' handles common target package tasks
INFO: Detected layers:
INFO: meta-qcom: LayerType.BSP, /srv/pokybuild/yocto-worker/check-layer-nightly/build/meta-qcom
INFO: 
INFO: Setting up for meta-qcom(LayerType.BSP), /srv/pokybuild/yocto-worker/check-layer-nightly/build/meta-qcom
INFO: Getting initial bitbake variables ...
INFO: Getting initial signatures ...
INFO: Adding layer meta-qcom
INFO: Starting to analyze: meta-qcom
INFO: Distro: nodistro
INFO: ----------------------------------------------------------------------
INFO: test_bsp_defines_machines (bsp.BSPCheckLayer.test_bsp_defines_machines)
INFO:  ... ok
INFO: test_bsp_no_set_machine (bsp.BSPCheckLayer.test_bsp_no_set_machine)
INFO:  ... ok
INFO: test_machine_signatures (bsp.BSPCheckLayer.test_machine_signatures)
INFO:  ... skipped 'No machines set with --machines.'
INFO: No machines set with --machines.
INFO: test_machine_world (bsp.BSPCheckLayer.test_machine_world)
INFO:  ... skipped 'No machines set with --machines.'
INFO: No machines set with --machines.
INFO: test_layerseries_compat (common.CommonCheckLayer.test_layerseries_compat)
INFO:  ... ok
INFO: test_parse (common.CommonCheckLayer.test_parse)
INFO:  ... ok
INFO: test_patches_upstream_status (common.CommonCheckLayer.test_patches_upstream_status)
INFO:  ... ok
INFO: test_readme (common.CommonCheckLayer.test_readme)
INFO:  ... FAIL
INFO: Traceback (most recent call last):
  File "/srv/pokybuild/yocto-worker/check-layer-nightly/build/layers/openembedded-core/scripts/lib/checklayer/cases/common.py", line 49, in test_readme
    self.assertIn('patch', data.lower(), msg="No patching information found in README.")
    ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'patch' not found in '# meta-qcom\n\n[![build on push (master)](https://img.shields.io/github/actions/workflow/status/qualcomm-linux/meta-qcom/push.yml?label=build%20on%20push%20(master))](https://github.com/qualcomm-linux/meta-qcom/actions/workflows/push.yml)\n[![nightly build (master)](https://img.shields.io/github/actions/workflow/status/qualcomm-linux/meta-qcom/nightly-build.yml?label=nightly%20build%20(master))](https://github.com/qualcomm-linux/meta-qcom/actions/workflows/nightly-build.yml)\n\n[![build on push (wrynose)](https://img.shields.io/github/actions/workflow/status/qualcomm-linux/meta-qcom/push.yml?branch=wrynose&label=build%20on%20push%20(wrynose))](https://github.com/qualcomm-linux/meta-qcom/actions/workflows/push.yml?query=branch%3awrynose)\n[![nightly build (wrynose)](https://img.shields.io/github/actions/workflow/status/qualcomm-linux/meta-qcom/nightly-build.yml?branch=wrynose&label=nightly%20build%20(wrynose))](https://github.com/qualcomm-linux/meta-qcom/actions/workflows/nightly-build.yml?query=branch%3awrynose)\n\n## introduction\n\n<img align="right" src="https://www.yoctoproject.org/wp-content/uploads/sites/32/2023/10/yoctocompatible1.jpg" alt="yocto compatible project badge" width="150"/>\n\nopenembedded/yocto project hardware enablement layer for qualcomm based platforms.\n\nthis layer provides additional recipes and machine configuration files for\nqualcomm platforms.\n\nthis layer depends on:\n\n```text\nuri: https://github.com/openembedded/openembedded-core.git\nlayers: meta\nbranch: master\nrevision: head\n```\n\nthis layer has an optional dependency on meta-oe layer:\n\n```text\nuri: https://github.com/openembedded/meta-openembedded.git\nlayers: meta-oe\nbranch: master\nrevision: head\n```\n\nthe dependency is optional, and not strictly required. when meta-oe is enabled\nin the build (e.g. it is used in bblayers) then additional recipes from\nmeta-qcom are added to the metadata. you can refer to meta-qcom/conf/layer.conf\nfor the implementation details.\n\n## branches\n\n- **master:** primary development branch, with focus on upstream support and\n  compatibility with the most recent yocto project release.\n- **wrynose:** lts branch based on the yocto project 6.0 release, used by\n  qualcomm linux 2.x.\n- **all stable branches up until styhead:** legacy branches maintained by linaro,\n  prior to the migration to [qualcomm-linux](https://github.com/qualcomm-linux).\n\n## machine support\n\nsee `conf/machine` for the complete list of supported devices.\n\n## generic machine support\n\nall contemporary boards are supported by a single qcom-armv8a machine. it can be\nused instead of using the per-board configuration file. in order to enable\nsupport for the particular device extend the qcom-armv8a.conf file.\n\n## quick build\n\nplease refer to the [yocto project reference manual](https://docs.yoctoproject.org/ref-manual/system-requirements.html)\nto set up your yocto project build environment.\n\nplease follow the instructions below for a kas-based build. the kas tool offers\nan easy way to setup bitbake based projects. for more details, visit the\n[kas documentation](https://kas.readthedocs.io/en/latest/index.html).\n\nthe steps below use `kas-container`, which runs the build inside a container,\nso the only host requirements are a container runtime (docker or podman) and\nthe `kas-container` wrapper script — kas, bitbake and the build dependencies do\nnot need to be installed on the host.\n\n1. get the `kas-container` script on your `path`\n   (from [kas-container](https://github.com/siemens/kas/blob/master/kas-container)).\n\n2. clone meta-qcom layer\n\n    ```bash\n    git clone https://github.com/qualcomm-linux/meta-qcom.git -b master\n    ```\n\n3. build using the kas configuration for one of the supported boards\n\n    ```bash\n    kas-container build meta-qcom/ci/rb3gen2-core-kit.yml\n    ```\n\nthis reuses the same `ci/<board>.yml` configurations that ci uses. see\n[agents.md](agents.md) for more advanced usage, including sharing the\n`dl_dir`/`sstate_dir` caches across builds.\n\n> **note:** to run kas natively on the host instead of in a container, install\n> kas by following the\n> [kas installation guide](https://kas.readthedocs.io/en/latest/userguide/getting-started.html#installation),\n> then use `kas build` in place of `kas-container build` in the steps above.\n\nfor a manual build without kas, refer to the [yocto project quick build](https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html).\n\n## flash\n\nfor instructions on building the qdl tool, preparing the board, and flashing\nimages over usb (edl mode), see [flashing images](docs/flashing.md).\n\n## security recommendations for production\n\nplease refer to the security recommendations for production builds documented here:\n[security recommendations](docs/security-recommendations.md)\n\n## releases\n\nmilestone releases for meta-qcom are managed directly in this repository\nusing git tags. each release tag captures the exact state of the layer for\nthat milestone, ensuring reproducible and stable builds. the list of available\nrelease tags can be found on the\n[meta-qcom tags page](https://github.com/qualcomm-linux/meta-qcom/tags).\n\nto build a specific release, clone the repository at the desired release tag and\nbuild it with kas using the configuration for your target machine and distro.\n\n1. clone meta-qcom at the release tag\n\n    ```bash\n    git clone https://github.com/qualcomm-linux/meta-qcom.git -b <meta-qcom-release-tag>\n    ```\n\n   replace `<meta-qcom-release-tag>` with the tag of the release you want to\n   build (see the [tags page](https://github.com/qualcomm-linux/meta-qcom/tags)).\n\n2. build using the kas configuration for your machine and distro\n\n    ```bash\n    kas build meta-qcom/ci/<machine>.yml:meta-qcom/ci/<distro>.yml\n    ```\n\n   replace `<machine>` with the target board and `<distro>` with the desired\n   distro configuration. for example:\n\n    ```bash\n    kas build meta-qcom/ci/rb3gen2-core-kit.yml:meta-qcom/ci/qcom-distro.yml\n    ```\n\n   refer to `meta-qcom/ci/` for the complete list of available machine and\n   distro configurations.\n\n## contributing\n\ncontributions are welcome. please read [contributing.md](contributing.md) for\nthe contribution workflow and the commit subject and message requirements\nbefore opening a pull request.\n\nbranch **kirkstone** is not open for direct contributions, please raise an\nissue with the suggested change instead.\n\n### qualcomm internal\n\nplease make sure to visit go/githubbasicsdoc and go/ossbestpractices before proposing changes.\n\n## communication\n\n- **github issues:** [meta-qcom issues](https://github.com/qualcomm-linux/meta-qcom/issues)\n- **pull requests:** [meta-qcom pull requests](https://github.com/qualcomm-linux/meta-qcom/pulls)\n\n## maintainer(s)\n\n- anuj mittal <anuj.mittal@oss.qualcomm.com>\n- dmitry baryshkov <dmitry.baryshkov@oss.qualcomm.com>\n- koen kooi <koen.kooi@oss.qualcomm.com>\n- nicolas dechesne <nicolas.dechesne@oss.qualcomm.com>\n- ricardo salveti <ricardo.salveti@oss.qualcomm.com>\n- sourabh banerjee <sbanerje@qti.qualcomm.com>\n- viswanath kraleti <viswanath.kraleti@oss.qualcomm.com>\n\n## license\n\nthis layer is licensed under the mit license. check out [copying.mit](copying.mit)\nfor more details.\n' : No patching information found in README.

INFO: test_security (common.CommonCheckLayer.test_security)
INFO:  ... ok
INFO: test_show_environment (common.CommonCheckLayer.test_show_environment)
INFO:  ... ok
INFO: test_signatures (common.CommonCheckLayer.test_signatures)
INFO:  ... ok
INFO: test_world (common.CommonCheckLayer.test_world)
INFO:  ... ok
INFO: test_world_inherit_class (common.CommonCheckLayer.test_world_inherit_class)
INFO:  ... ok
INFO: setUpClass (distro.DistroCheckLayer)
INFO:  ... skipped "DistroCheckLayer: Layer meta-qcom isn't Distro one."
INFO: ======================================================================
INFO: FAIL: test_readme (common.CommonCheckLayer.test_readme)
INFO: ----------------------------------------------------------------------
INFO: Traceback (most recent call last):
  File "/srv/pokybuild/yocto-worker/check-layer-nightly/build/layers/openembedded-core/scripts/lib/checklayer/cases/common.py", line 49, in test_readme
    self.assertIn('patch', data.lower(), msg="No patching information found in README.")
    ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: 'patch' not found in '# meta-qcom\n\n[![build on push (master)](https://img.shields.io/github/actions/workflow/status/qualcomm-linux/meta-qcom/push.yml?label=build%20on%20push%20(master))](https://github.com/qualcomm-linux/meta-qcom/actions/workflows/push.yml)\n[![nightly build (master)](https://img.shields.io/github/actions/workflow/status/qualcomm-linux/meta-qcom/nightly-build.yml?label=nightly%20build%20(master))](https://github.com/qualcomm-linux/meta-qcom/actions/workflows/nightly-build.yml)\n\n[![build on push (wrynose)](https://img.shields.io/github/actions/workflow/status/qualcomm-linux/meta-qcom/push.yml?branch=wrynose&label=build%20on%20push%20(wrynose))](https://github.com/qualcomm-linux/meta-qcom/actions/workflows/push.yml?query=branch%3awrynose)\n[![nightly build (wrynose)](https://img.shields.io/github/actions/workflow/status/qualcomm-linux/meta-qcom/nightly-build.yml?branch=wrynose&label=nightly%20build%20(wrynose))](https://github.com/qualcomm-linux/meta-qcom/actions/workflows/nightly-build.yml?query=branch%3awrynose)\n\n## introduction\n\n<img align="right" src="https://www.yoctoproject.org/wp-content/uploads/sites/32/2023/10/yoctocompatible1.jpg" alt="yocto compatible project badge" width="150"/>\n\nopenembedded/yocto project hardware enablement layer for qualcomm based platforms.\n\nthis layer provides additional recipes and machine configuration files for\nqualcomm platforms.\n\nthis layer depends on:\n\n```text\nuri: https://github.com/openembedded/openembedded-core.git\nlayers: meta\nbranch: master\nrevision: head\n```\n\nthis layer has an optional dependency on meta-oe layer:\n\n```text\nuri: https://github.com/openembedded/meta-openembedded.git\nlayers: meta-oe\nbranch: master\nrevision: head\n```\n\nthe dependency is optional, and not strictly required. when meta-oe is enabled\nin the build (e.g. it is used in bblayers) then additional recipes from\nmeta-qcom are added to the metadata. you can refer to meta-qcom/conf/layer.conf\nfor the implementation details.\n\n## branches\n\n- **master:** primary development branch, with focus on upstream support and\n  compatibility with the most recent yocto project release.\n- **wrynose:** lts branch based on the yocto project 6.0 release, used by\n  qualcomm linux 2.x.\n- **all stable branches up until styhead:** legacy branches maintained by linaro,\n  prior to the migration to [qualcomm-linux](https://github.com/qualcomm-linux).\n\n## machine support\n\nsee `conf/machine` for the complete list of supported devices.\n\n## generic machine support\n\nall contemporary boards are supported by a single qcom-armv8a machine. it can be\nused instead of using the per-board configuration file. in order to enable\nsupport for the particular device extend the qcom-armv8a.conf file.\n\n## quick build\n\nplease refer to the [yocto project reference manual](https://docs.yoctoproject.org/ref-manual/system-requirements.html)\nto set up your yocto project build environment.\n\nplease follow the instructions below for a kas-based build. the kas tool offers\nan easy way to setup bitbake based projects. for more details, visit the\n[kas documentation](https://kas.readthedocs.io/en/latest/index.html).\n\nthe steps below use `kas-container`, which runs the build inside a container,\nso the only host requirements are a container runtime (docker or podman) and\nthe `kas-container` wrapper script — kas, bitbake and the build dependencies do\nnot need to be installed on the host.\n\n1. get the `kas-container` script on your `path`\n   (from [kas-container](https://github.com/siemens/kas/blob/master/kas-container)).\n\n2. clone meta-qcom layer\n\n    ```bash\n    git clone https://github.com/qualcomm-linux/meta-qcom.git -b master\n    ```\n\n3. build using the kas configuration for one of the supported boards\n\n    ```bash\n    kas-container build meta-qcom/ci/rb3gen2-core-kit.yml\n    ```\n\nthis reuses the same `ci/<board>.yml` configurations that ci uses. see\n[agents.md](agents.md) for more advanced usage, including sharing the\n`dl_dir`/`sstate_dir` caches across builds.\n\n> **note:** to run kas natively on the host instead of in a container, install\n> kas by following the\n> [kas installation guide](https://kas.readthedocs.io/en/latest/userguide/getting-started.html#installation),\n> then use `kas build` in place of `kas-container build` in the steps above.\n\nfor a manual build without kas, refer to the [yocto project quick build](https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html).\n\n## flash\n\nfor instructions on building the qdl tool, preparing the board, and flashing\nimages over usb (edl mode), see [flashing images](docs/flashing.md).\n\n## security recommendations for production\n\nplease refer to the security recommendations for production builds documented here:\n[security recommendations](docs/security-recommendations.md)\n\n## releases\n\nmilestone releases for meta-qcom are managed directly in this repository\nusing git tags. each release tag captures the exact state of the layer for\nthat milestone, ensuring reproducible and stable builds. the list of available\nrelease tags can be found on the\n[meta-qcom tags page](https://github.com/qualcomm-linux/meta-qcom/tags).\n\nto build a specific release, clone the repository at the desired release tag and\nbuild it with kas using the configuration for your target machine and distro.\n\n1. clone meta-qcom at the release tag\n\n    ```bash\n    git clone https://github.com/qualcomm-linux/meta-qcom.git -b <meta-qcom-release-tag>\n    ```\n\n   replace `<meta-qcom-release-tag>` with the tag of the release you want to\n   build (see the [tags page](https://github.com/qualcomm-linux/meta-qcom/tags)).\n\n2. build using the kas configuration for your machine and distro\n\n    ```bash\n    kas build meta-qcom/ci/<machine>.yml:meta-qcom/ci/<distro>.yml\n    ```\n\n   replace `<machine>` with the target board and `<distro>` with the desired\n   distro configuration. for example:\n\n    ```bash\n    kas build meta-qcom/ci/rb3gen2-core-kit.yml:meta-qcom/ci/qcom-distro.yml\n    ```\n\n   refer to `meta-qcom/ci/` for the complete list of available machine and\n   distro configurations.\n\n## contributing\n\ncontributions are welcome. please read [contributing.md](contributing.md) for\nthe contribution workflow and the commit subject and message requirements\nbefore opening a pull request.\n\nbranch **kirkstone** is not open for direct contributions, please raise an\nissue with the suggested change instead.\n\n### qualcomm internal\n\nplease make sure to visit go/githubbasicsdoc and go/ossbestpractices before proposing changes.\n\n## communication\n\n- **github issues:** [meta-qcom issues](https://github.com/qualcomm-linux/meta-qcom/issues)\n- **pull requests:** [meta-qcom pull requests](https://github.com/qualcomm-linux/meta-qcom/pulls)\n\n## maintainer(s)\n\n- anuj mittal <anuj.mittal@oss.qualcomm.com>\n- dmitry baryshkov <dmitry.baryshkov@oss.qualcomm.com>\n- koen kooi <koen.kooi@oss.qualcomm.com>\n- nicolas dechesne <nicolas.dechesne@oss.qualcomm.com>\n- ricardo salveti <ricardo.salveti@oss.qualcomm.com>\n- sourabh banerjee <sbanerje@qti.qualcomm.com>\n- viswanath kraleti <viswanath.kraleti@oss.qualcomm.com>\n\n## license\n\nthis layer is licensed under the mit license. check out [copying.mit](copying.mit)\nfor more details.\n' : No patching information found in README.

INFO: ----------------------------------------------------------------------
INFO: Ran 13 tests in 116.819s
INFO: FAILED
INFO:  (failures=1, skipped=3)
INFO: 
INFO: Summary of results:
INFO: 
INFO: meta-qcom ... FAIL