[yocto] [auto-upgrade-helper][PATCH] bitbake: consider both stdout and stderr when checking or logging output
Signed-off-by: Alexander Kanavin
---
modules/buildhistory.py | 2 +-
modules/steps.py | 4 ++--
modules/testimage.py | 4 ++--
modules/utils/bitbake.py | 2 +-
upgrade-helper.py| 4 ++--
5 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/modules/buildhistory.py b/modules/buildhistory.py
index 6649023..e0f7191 100644
--- a/modules/buildhistory.py
+++ b/modules/buildhistory.py
@@ -43,7 +43,7 @@ class BuildHistory(object):
try:
self.bb.complete(self.pn, machine)
except Error as e:
-for line in e.stdout.split("\n"):
+for line in e.stdout.split("\n") + e.stderr.split("\n"):
# version going backwards is not a real error
if re.match(".* went backwards which would break package
feeds .*", line):
break
diff --git a/modules/steps.py b/modules/steps.py
index 811b88d..bde72db 100644
--- a/modules/steps.py
+++ b/modules/steps.py
@@ -107,8 +107,8 @@ def _compile(bb, pkg, machine, workdir):
bb.complete(pkg, machine)
except Error as e:
with open("{}/bitbake-output-{}.txt".format(workdir, machine),
'w') as f:
-f.write(e.stdout)
-for line in e.stdout.split("\n"):
+f.write(e.stdout + e.stderr)
+for line in e.stdout.split("\n") + e.stderr.split("\n"):
# version going backwards is not a real error
if re.match(".* went backwards which would break package feeds
.*", line):
break
diff --git a/modules/testimage.py b/modules/testimage.py
index 4272c84..0fc1adb 100644
--- a/modules/testimage.py
+++ b/modules/testimage.py
@@ -85,14 +85,14 @@ class TestImage():
bitbake_create_output = self.bb.complete(image, machine)
except Error as e:
I( " building the testimage failed! Collecting logs...")
-bitbake_create_output = e.stdout
+bitbake_create_output = e.stdout + e.stderr
else:
I( " running %s/testimage for %s ..." % (image, machine))
try:
bitbake_run_output = self.bb.complete("%s -c testimage" %
image, machine)
except Error as e:
I( " running the testimage failed! Collecting logs...")
-bitbake_run_output = e.stdout
+bitbake_run_output = e.stdout + e.stderr
if bitbake_create_output:
with open(os.path.join(self.logdir,
"bitbake-create-testimage.log"), 'w') as f:
diff --git a/modules/utils/bitbake.py b/modules/utils/bitbake.py
index 4835ca6..a5fc6fa 100644
--- a/modules/utils/bitbake.py
+++ b/modules/utils/bitbake.py
@@ -73,7 +73,7 @@ class Bitbake(object):
if self.log_dir is not None and os.path.exists(self.log_dir):
with open(os.path.join(self.log_dir, BITBAKE_ERROR_LOG), "a+")
as log:
-log.write(e.stdout)
+log.write(e.stdout + e.stderr)
raise Error("\'" + cmd + "\' failed", e.stdout, e.stderr)
diff --git a/upgrade-helper.py b/upgrade-helper.py
index eb3935e..ecdabb0 100755
--- a/upgrade-helper.py
+++ b/upgrade-helper.py
@@ -153,7 +153,7 @@ class Updater(object):
except EmptyEnvError as e:
import traceback
E( " %s\n%s" % (e.message, traceback.format_exc()))
-E( " Bitbake output:\n%s" % (e.stdout))
+E( " Bitbake output:\n%s" % (e.stdout + e.stderr))
exit(1)
self._set_options()
@@ -459,7 +459,7 @@ class Updater(object):
E(" Can't build gcc-runtime for %s." % machine)
if isinstance(e, Error):
-E(e.stdout)
+E(e.stdout + e.stderr)
else:
import traceback
traceback.print_exc(file=sys.stdout)
--
2.33.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55653): https://lists.yoctoproject.org/g/yocto/message/55653
Mute This Topic: https://lists.yoctoproject.org/mt/87925476/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] meta-virtualization/docker/containerd issue seen
Nevermind… I forgot if you have added the docker-ce recipe to the build then it does spawn the docker daemon automatically, even if it’s sysvinit… Thanks anyway, and Happy Holidays… From: yocto@lists.yoctoproject.org On Behalf Of Monsees, Steven C (US) via lists.yoctoproject.org Sent: Thursday, December 23, 2021 1:27 PM To: yocto@lists.yoctoproject.org Subject: [yocto] meta-virtualization/docker/containerd issue seen External Email Alert This email has been sent from an account outside of the BAE Systems network. Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros. For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar. I am trying to build in basic docker functionality for container support… I am zeus based, and am building docker and docker-ce-contrib. When I manually start the dockerd in the background I am seeing a timeout when attempting to use containerd. Any ideas as ti why I am getting this error or how I might resolve it ? (see bottom) Thanks, Steve Initialization complete. Sending init complete message Running indefinitely root@sbca-default which docker /usr/bin/docker root@sbca-default docker --version Docker version 19.03.2-ce, build 6a30dfc root@sbca-default docker info Client: Debug Mode: false Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 19.03.2-ce Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: fd103cb716352c7e19768e4fed057f71d68902a0.m runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f-dirty init version: fec3683-dirty (expected: fec3683b971d9) Kernel Version: 4.19.135-intel-pk-standard OSType: linux Architecture: x86_64 CPUs: 8 Total Memory: 15.51GiB Name: sbca-default ID: YFQW:EPJT:TSJU:C64F:NU57:RAJL:X5IC:J5IT:MRTP:SIGS:RI25:KUFQ Docker Root Dir: /var/lib/docker Debug Mode: false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: localhost:5000 127.0.0.0/8 Registry Mirrors: http://localhost:5000/ Live Restore Enabled: false root@sbca-default /usr/share/docker/check-config.sh info: reading kernel config from /proc/config.gz ... Generally Necessary: - cgroup hierarchy: properly mounted [/sys/fs/cgroup] - CONFIG_NAMESPACES: enabled - CONFIG_NET_NS: enabled - CONFIG_PID_NS: enabled - CONFIG_IPC_NS: enabled - CONFIG_UTS_NS: enabled - CONFIG_CGROUPS: enabled - CONFIG_CGROUP_CPUACCT: enabled - CONFIG_CGROUP_DEVICE: enabled - CONFIG_CGROUP_FREEZER: enabled - CONFIG_CGROUP_SCHED: enabled - CONFIG_CPUSETS: enabled - CONFIG_MEMCG: enabled - CONFIG_KEYS: enabled - CONFIG_VETH: enabled - CONFIG_BRIDGE: enabled (as module) - CONFIG_BRIDGE_NETFILTER: enabled (as module) - CONFIG_NF_NAT_IPV4: enabled (as module) - CONFIG_IP_NF_FILTER: enabled (as module) - CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_IPVS: enabled (as module) - CONFIG_IP_NF_NAT: enabled (as module) - CONFIG_NF_NAT: enabled (as module) - CONFIG_NF_NAT_NEEDED: enabled - CONFIG_POSIX_MQUEUE: enabled Optional Features: - CONFIG_USER_NS: enabled - CONFIG_SECCOMP: enabled - CONFIG_CGROUP_PIDS: enabled - CONFIG_MEMCG_SWAP: enabled - CONFIG_MEMCG_SWAP_ENABLED: enabled (cgroup swap accounting is currently enabled) - CONFIG_LEGACY_VSYSCALL_EMULATE: enabled - CONFIG_BLK_CGROUP: enabled - CONFIG_BLK_DEV_THROTTLING: enabled - CONFIG_IOSCHED_CFQ: enabled - CONFIG_CFQ_GROUP_IOSCHED: enabled - CONFIG_CGROUP_PERF: enabled - CONFIG_CGROUP_HUGETLB: enabled - CONFIG_NET_CLS_CGROUP: enabled - CONFIG_CGROUP_NET_PRIO: enabled - CONFIG_CFS_BANDWIDTH: enabled - CONFIG_FAIR_GROUP_SCHED: enabled - CONFIG_RT_GROUP_SCHED: enabled - CONFIG_IP_NF_TARGET_REDIRECT: enabled (as module) - CONFIG_IP_VS: enabled (as module) - CONFIG_IP_VS_NFCT: enabled - CONFIG_IP_VS_PROTO_TCP: enabled - CONFIG_IP_VS_PROTO_UDP: enabled - CONFIG_IP_VS_RR: enabled (as module) - CONFIG_EXT4_FS: enabled - CONFIG_EXT4_FS_POSIX_ACL: enabled - CONFIG_EXT4_FS_SECURITY: enabled - Network Drivers: - "overlay": - CONFIG_VXLAN: enabled Optional (for encrypted networks): - CONFIG_CRYPTO: enabled - CONFIG_CRYPTO_AEAD: enabled - CONFIG_CRYPTO_GCM: enabled (as module) - CONFIG_CRYPTO_SEQIV: enabled - CONFIG_CRYPTO_GHASH: enabled (as module) - CONFIG_XFRM: enabled - CONFIG_XFRM_USER: enabled (as module) - CONFIG_XFRM_ALGO:
[yocto] meta-virtualization/docker/containerd issue seen
I am trying to build in basic docker functionality for container support... I am zeus based, and am building docker and docker-ce-contrib. When I manually start the dockerd in the background I am seeing a timeout when attempting to use containerd. Any ideas as ti why I am getting this error or how I might resolve it ? (see bottom) Thanks, Steve Initialization complete. Sending init complete message Running indefinitely root@sbca-default which docker /usr/bin/docker root@sbca-default docker --version Docker version 19.03.2-ce, build 6a30dfc root@sbca-default docker info Client: Debug Mode: false Server: Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 19.03.2-ce Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: fd103cb716352c7e19768e4fed057f71d68902a0.m runc version: 425e105d5a03fabd737a126ad93d62a9eeede87f-dirty init version: fec3683-dirty (expected: fec3683b971d9) Kernel Version: 4.19.135-intel-pk-standard OSType: linux Architecture: x86_64 CPUs: 8 Total Memory: 15.51GiB Name: sbca-default ID: YFQW:EPJT:TSJU:C64F:NU57:RAJL:X5IC:J5IT:MRTP:SIGS:RI25:KUFQ Docker Root Dir: /var/lib/docker Debug Mode: false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: localhost:5000 127.0.0.0/8 Registry Mirrors: http://localhost:5000/ Live Restore Enabled: false root@sbca-default /usr/share/docker/check-config.sh info: reading kernel config from /proc/config.gz ... Generally Necessary: - cgroup hierarchy: properly mounted [/sys/fs/cgroup] - CONFIG_NAMESPACES: enabled - CONFIG_NET_NS: enabled - CONFIG_PID_NS: enabled - CONFIG_IPC_NS: enabled - CONFIG_UTS_NS: enabled - CONFIG_CGROUPS: enabled - CONFIG_CGROUP_CPUACCT: enabled - CONFIG_CGROUP_DEVICE: enabled - CONFIG_CGROUP_FREEZER: enabled - CONFIG_CGROUP_SCHED: enabled - CONFIG_CPUSETS: enabled - CONFIG_MEMCG: enabled - CONFIG_KEYS: enabled - CONFIG_VETH: enabled - CONFIG_BRIDGE: enabled (as module) - CONFIG_BRIDGE_NETFILTER: enabled (as module) - CONFIG_NF_NAT_IPV4: enabled (as module) - CONFIG_IP_NF_FILTER: enabled (as module) - CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_IPVS: enabled (as module) - CONFIG_IP_NF_NAT: enabled (as module) - CONFIG_NF_NAT: enabled (as module) - CONFIG_NF_NAT_NEEDED: enabled - CONFIG_POSIX_MQUEUE: enabled Optional Features: - CONFIG_USER_NS: enabled - CONFIG_SECCOMP: enabled - CONFIG_CGROUP_PIDS: enabled - CONFIG_MEMCG_SWAP: enabled - CONFIG_MEMCG_SWAP_ENABLED: enabled (cgroup swap accounting is currently enabled) - CONFIG_LEGACY_VSYSCALL_EMULATE: enabled - CONFIG_BLK_CGROUP: enabled - CONFIG_BLK_DEV_THROTTLING: enabled - CONFIG_IOSCHED_CFQ: enabled - CONFIG_CFQ_GROUP_IOSCHED: enabled - CONFIG_CGROUP_PERF: enabled - CONFIG_CGROUP_HUGETLB: enabled - CONFIG_NET_CLS_CGROUP: enabled - CONFIG_CGROUP_NET_PRIO: enabled - CONFIG_CFS_BANDWIDTH: enabled - CONFIG_FAIR_GROUP_SCHED: enabled - CONFIG_RT_GROUP_SCHED: enabled - CONFIG_IP_NF_TARGET_REDIRECT: enabled (as module) - CONFIG_IP_VS: enabled (as module) - CONFIG_IP_VS_NFCT: enabled - CONFIG_IP_VS_PROTO_TCP: enabled - CONFIG_IP_VS_PROTO_UDP: enabled - CONFIG_IP_VS_RR: enabled (as module) - CONFIG_EXT4_FS: enabled - CONFIG_EXT4_FS_POSIX_ACL: enabled - CONFIG_EXT4_FS_SECURITY: enabled - Network Drivers: - "overlay": - CONFIG_VXLAN: enabled Optional (for encrypted networks): - CONFIG_CRYPTO: enabled - CONFIG_CRYPTO_AEAD: enabled - CONFIG_CRYPTO_GCM: enabled (as module) - CONFIG_CRYPTO_SEQIV: enabled - CONFIG_CRYPTO_GHASH: enabled (as module) - CONFIG_XFRM: enabled - CONFIG_XFRM_USER: enabled (as module) - CONFIG_XFRM_ALGO: enabled - CONFIG_INET_ESP: enabled (as module) - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled - "ipvlan": - CONFIG_IPVLAN: enabled - "macvlan": - CONFIG_MACVLAN: enabled - CONFIG_DUMMY: enabled - "ftp,tftp client in container": - CONFIG_NF_NAT_FTP: enabled (as module) - CONFIG_NF_CONNTRACK_FTP: enabled (as module) - CONFIG_NF_NAT_TFTP: enabled (as module) - CONFIG_NF_CONNTRACK_TFTP: enabled (as module) - Storage Drivers: - "aufs": - CONFIG_AUFS_FS: missing - "btrfs": - CONFIG_BTRFS_FS: enabled - CONFIG_BTRFS_FS_POSIX_ACL: enabled - "devicemapper": - CONFIG_BLK_DEV_DM: enabled - CONFIG_DM_THIN_PROVISIONING: enabled - "overlay": - CONFIG_OVERLAY_FS: enabled - "zfs": - /dev/zfs: missing - zfs command: missing - zpool command: missing Limits: -
[yocto] Minutes: Yocto Project Weekly Triage Meeting 12/23/2021
*Wiki: *https://wiki.yoctoproject.org/wiki/Bug_Triage *Attendees: *Randy, Richard, Saul, Stephen, Steve, Trevor *ARs:* Happy Holidays! *Notes:* No triage meeting on December 30th *Medium+ 3.5 Unassigned Enhancements/Bugs: *75 (Last week 76) *Medium+ 3.99 Unassigned Enhancements/Bugs: *38**(Last week 38) *AB Bugs: *70 (Last week 73) -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55650): https://lists.yoctoproject.org/g/yocto/message/55650 Mute This Topic: https://lists.yoctoproject.org/mt/87920883/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] Where to define udev to load kernel modules in boot?
Hi JH, On December 23, 2021 11:28:55 AM GMT+01:00, JH wrote: >Hi, > >I built an OE/Yocto IoT device to include kernel modules of usb_wwan, >usbserial, mwifiex_sdio, mwifiex etc, there is one udev from >meta-freescale/recipes-core/udev/udev-rules-imx/10-imx.rules > ># ls /etc/udev/rules.d >10-imx.rules touchscreen.rules > >My device does not have a touchscreen so that touchscreen.rules should >not be there. The 10-imx.rules does not define any kernel modules >usb_wwan, usbserial, mwifiex_sdio, mwifiex, the device does not have >video or any input > ># cat /etc/udev/rules.d/10-imx.rules >KERNEL=="mc13783_connectiv*", NAME="mc13783_connectivity" ># Anyone has readonly permission to IIM device file >KERNEL=="mxc_iim", MODE="0444", SYMLINK+="mxc_mem" >KERNEL=="mxs_viim", MODE="0444", SYMLINK+="mxc_mem" >KERNEL=="mxc_ipu", MODE="0666" >KERNEL=="mxc_vpu", MODE="0666" >SUBSYSTEM=="video", MODE="0660" >KERNEL=="fb[0-9]", MODE="0660", GROUP="video" >KERNEL=="gsl_kmod", MODE="0660", GROUP="video" >KERNEL=="galcore", MODE="0660", GROUP="video" > >How can I define udev in recipes to make the system to load kernel >modules of usb_wwan, usbserial, mwifiex_sdio, mwifiex in boot? > IIRC, you need to add your package to KERNEL_MODULE_AUTOLOAD, c.f. https://docs.yoctoproject.org/ref-manual/variables.html#term-KERNEL_MODULE_AUTOLOAD Cheers, Quentin >Thank you. > >Kind regards, > >- jh -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55649): https://lists.yoctoproject.org/g/yocto/message/55649 Mute This Topic: https://lists.yoctoproject.org/mt/87915884/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Where to define udev to load kernel modules in boot?
Hi, I built an OE/Yocto IoT device to include kernel modules of usb_wwan, usbserial, mwifiex_sdio, mwifiex etc, there is one udev from meta-freescale/recipes-core/udev/udev-rules-imx/10-imx.rules # ls /etc/udev/rules.d 10-imx.rules touchscreen.rules My device does not have a touchscreen so that touchscreen.rules should not be there. The 10-imx.rules does not define any kernel modules usb_wwan, usbserial, mwifiex_sdio, mwifiex, the device does not have video or any input # cat /etc/udev/rules.d/10-imx.rules KERNEL=="mc13783_connectiv*", NAME="mc13783_connectivity" # Anyone has readonly permission to IIM device file KERNEL=="mxc_iim", MODE="0444", SYMLINK+="mxc_mem" KERNEL=="mxs_viim", MODE="0444", SYMLINK+="mxc_mem" KERNEL=="mxc_ipu", MODE="0666" KERNEL=="mxc_vpu", MODE="0666" SUBSYSTEM=="video", MODE="0660" KERNEL=="fb[0-9]", MODE="0660", GROUP="video" KERNEL=="gsl_kmod", MODE="0660", GROUP="video" KERNEL=="galcore", MODE="0660", GROUP="video" How can I define udev in recipes to make the system to load kernel modules of usb_wwan, usbserial, mwifiex_sdio, mwifiex in boot? Thank you. Kind regards, - jh -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55648): https://lists.yoctoproject.org/g/yocto/message/55648 Mute This Topic: https://lists.yoctoproject.org/mt/87915884/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
