Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.29.rc1)

2023-11-02 Thread Jing Hui Tham
Hi All, QA for yocto-3.1.29.rc1 is completed. This is the full report for this release: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults === Summary No high milestone defects. No new issue found. Thanks, Jing Hui > -

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.29.rc1)

2023-10-29 Thread Jing Hui Tham
Hi all, Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.29.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw Runtime auto test for following platforms: 1. MinnowBoard Turbot - 32bit

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.29.rc1)

2023-10-28 Thread Steve Sakoman
On Fri, Oct 27, 2023 at 10:30 PM Richard Purdie wrote: > > On Fri, 2023-10-27 at 12:38 -1000, Steve Sakoman wrote: > > There is currently a known reproducibility issue with the vim-common > > package. In my opinion nothing that should hold up the release. > > > > Details: > > > > It seems that th

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.29.rc1)

2023-10-28 Thread Richard Purdie
On Fri, 2023-10-27 at 12:38 -1000, Steve Sakoman wrote: > There is currently a known reproducibility issue with the vim-common > package. In my opinion nothing that should hold up the release. > > Details: > > It seems that the last sstate build of vim was done on an Ubuntu 22.04 > worker and re

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.29.rc1)

2023-10-27 Thread Steve Sakoman
There is currently a known reproducibility issue with the vim-common package. In my opinion nothing that should hold up the release. Details: It seems that the last sstate build of vim was done on an Ubuntu 22.04 worker and recent changes there seem to result in an occurance of "charset=cp1251"