Current Dev Position: YP 3.4 M4 Next Deadline: 29th Oct. 2021 YP 3.4 M4 release Next Team Meetings: Bug Triage meeting Thursday Oct. 21st at 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y

I can see why this breaks and it isn't entirely straightforward to fix since we'd have to add data to the file-checksums entries which are generated by both OE and Bitbake. I have a bit of a horrible

Since that build directory contains symlinks, we may need something like cp -L here? I didn't test but I think we might run into an issue? Cheers, Richard

A build flagged for QA (yocto-3.4.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.4.rc1 Build hash information: bitbake: c78ebac71ec976fdf2

The symlinks will be in the XXX-dev packages so boost-dev probably has them for boost. They aren't needed on target unless you're compiling things which is why they're separated out. Cheers, Richard

I did look at it. It was using a modified oe-selftest with threading instead of multiprocess. We're not using that so I closed it. Cheers, Richard

The file is being created with python's tempfile function which will make it secure. Secure in this context means 00600... I suspect you're right that creating a file securely here with this permissio

Hard to say without understanding how it failed. What was the error? You probably need to match python3 and python3-native versions but I don't know if you did. Cheers, Richard

I'm not sure about this since it has the potential to add a lot of files to the release directories and I suspect that will confuse the releases and people looking at them. At the very least we need t

It is great to see this. I'd suggest dmesg in here since we've seen components of tests segfault before (e.g. lttng-relayd in lttng-tools). Cheers, Richard

A build flagged for QA (yocto-3.1.11.rc2) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.1.11.rc2 Build hash information: bitbake: c2a3bda3a29e

A build flagged for QA (yocto-3.1.11.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.1.11.rc1 Build hash information: bitbake: c2a3bda3a29e

wrote: Upstream gave this as an example which I think we can probably do something with: from datetime import datetime, timedelta from dateutil.tz import tzutc from twisted.internet import defer # thi

We did merge and start using this. Unfortunately whilst I thought it would work, it has some unfortunate side effects and we'll probably have to disable it. If you have two build requests for say "a-f

In general you need the sstate and the PR server to match. Using multiple different pools of sstate with the same PR server will probably not work so well. It won't matter about DL_DIR or PERSISTENT_D

A build flagged for QA (yocto-3.3.3.rc2) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.3.3.rc2 Build hash information: bitbake: c7b506d11df78c

Hi, I think there is a patch queued in the testing branch for dunfell: http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=stable/dunfell-nut http://git.yoctoproject.org/cgit.cgi/poky-contrib/com

Hi, Thanks for the patch. This isn't ready to be merged yet though as there are some issues. This isn't true, they are looked at first in bitbake's datastore, then taken from the original host environ

A build flagged for QA (yocto-3.3.3.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.3.3.rc1 Build hash information: bitbake: 9b2d96b27f550d

A build flagged for QA (yocto-3.4_M3.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-3.4_M3.rc1 Build hash information: bitbake: 0a11696e0898