[yocto] [PATCH 1/2] patchtest: fix virtio-9p-pci is not a valid device
From: Changqing Li fix error during runqemu: test_mount: 'virtio-9p-pci' is not a valid device model name recipe qemu has been splited into qemu/qemu-native/qemu-sytem-native Signed-off-by: Changqing Li --- meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend | 1 + meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend | 1 - 2 files changed, 1 insertion(+), 1 deletion(-) create mode 100644 meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend delete mode 100644 meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend diff --git a/meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend b/meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend new file mode 100644 index 000..a91ccb7 --- /dev/null +++ b/meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend @@ -0,0 +1 @@ +PACKAGECONFIG_append = " virtfs" diff --git a/meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend b/meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend deleted file mode 100644 index 3ad9f03..000 --- a/meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend +++ /dev/null @@ -1 +0,0 @@ -PACKAGECONFIG_append_pn-qemu-native = " virtfs" -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [patchtest][PATCH 1/2] patchtest: fix virtio-9p-pci is not a valid device
From: Changqing Li fix error during runqemu: test_mount: 'virtio-9p-pci' is not a valid device model name recipe qemu has been splited into qemu/qemu-native/qemu-sytem-native Signed-off-by: Changqing Li --- meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend | 1 + meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend | 1 - 2 files changed, 1 insertion(+), 1 deletion(-) create mode 100644 meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend delete mode 100644 meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend diff --git a/meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend b/meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend new file mode 100644 index 000..a91ccb7 --- /dev/null +++ b/meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend @@ -0,0 +1 @@ +PACKAGECONFIG_append = " virtfs" diff --git a/meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend b/meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend deleted file mode 100644 index 3ad9f03..000 --- a/meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend +++ /dev/null @@ -1 +0,0 @@ -PACKAGECONFIG_append_pn-qemu-native = " virtfs" -- 2.7.4 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [patchtest][PATCH 2/2] patchtest: fix linux-yocto version
From: Changqing Li
4.9 is not avaiable currently, preferred version changed
to 5.0, also correct the bbappend name
Signed-off-by: Changqing Li
---
.../linux/{linux-yocto_4.%.bbappend => linux-yocto_%.bbappend} | 0
scripts/create-guest-machine | 5 +
2 files changed, 1 insertion(+), 4 deletions(-)
rename meta-patchtest/recipes-kernel/linux/{linux-yocto_4.%.bbappend =>
linux-yocto_%.bbappend} (100%)
diff --git a/meta-patchtest/recipes-kernel/linux/linux-yocto_4.%.bbappend
b/meta-patchtest/recipes-kernel/linux/linux-yocto_%.bbappend
similarity index 100%
rename from meta-patchtest/recipes-kernel/linux/linux-yocto_4.%.bbappend
rename to meta-patchtest/recipes-kernel/linux/linux-yocto_%.bbappend
diff --git a/scripts/create-guest-machine b/scripts/create-guest-machine
index 8dd6a2e..151d5c2 100755
--- a/scripts/create-guest-machine
+++ b/scripts/create-guest-machine
@@ -145,10 +145,7 @@ cat >> $POKY/build/conf/auto.conf << EOF
$PTSMARK
MACHINE = "$MACHINE"
-# The preferred kernel version in poky (4.10%, master) returns an error whilst
-# executing patchtest on guest. Changing the preferred version to 4.9% as it
-# is more suitable and does not present any errors.
-PREFERRED_VERSION_linux-yocto_qemux86-64 = "4.9%"
+PREFERRED_VERSION_linux-yocto_qemux86-64 = "5.0%"
PACKAGE_CLASSES = "package_ipk"
IMAGE_FSTYPES = "ext4"
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [autobuilder] Y-AB in a docker container?
Hi, I use the good old yocto autobuilder in a docker container and it still serves me well, but I would like to move to the shiny new yocto autobuilder. Before I start spending hours to do it myself I wonder if someone already did something like this and is willing to share the Dockerfile(s). Regards, Robert -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH 1/2] patchtest: fix virtio-9p-pci is not a valid device
Please ignore this one, I resend one. On 6/13/19 3:45 PM, changqing...@windriver.com wrote: From: Changqing Li fix error during runqemu: test_mount: 'virtio-9p-pci' is not a valid device model name recipe qemu has been splited into qemu/qemu-native/qemu-sytem-native Signed-off-by: Changqing Li --- meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend | 1 + meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend | 1 - 2 files changed, 1 insertion(+), 1 deletion(-) create mode 100644 meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend delete mode 100644 meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend diff --git a/meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend b/meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend new file mode 100644 index 000..a91ccb7 --- /dev/null +++ b/meta-patchtest/recipes-devtools/qemu/qemu-system-native_%.bbappend @@ -0,0 +1 @@ +PACKAGECONFIG_append = " virtfs" diff --git a/meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend b/meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend deleted file mode 100644 index 3ad9f03..000 --- a/meta-patchtest/recipes-devtools/qemu/qemu_%.bbappend +++ /dev/null @@ -1 +0,0 @@ -PACKAGECONFIG_append_pn-qemu-native = " virtfs" -- BRs Sandy(Li Changqing) -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [patchtest][PATCH 2/2] patchtest: fix linux-yocto version
On Thu, Jun 13, 2019 at 03:46:04PM +0800, changqing...@windriver.com wrote: > From: Changqing Li > > 4.9 is not avaiable currently, preferred version changed > to 5.0, also correct the bbappend name 5.0 is already EOL upstream and will be removed soon. >... > --- a/scripts/create-guest-machine > +++ b/scripts/create-guest-machine > @@ -145,10 +145,7 @@ cat >> $POKY/build/conf/auto.conf << EOF > $PTSMARK > MACHINE = "$MACHINE" > > -# The preferred kernel version in poky (4.10%, master) returns an error > whilst > -# executing patchtest on guest. Changing the preferred version to 4.9% as it > -# is more suitable and does not present any errors. > -PREFERRED_VERSION_linux-yocto_qemux86-64 = "4.9%" > +PREFERRED_VERSION_linux-yocto_qemux86-64 = "5.0%" >... This looks as if it was a temporary workaround for some problem with kernel 4.10. If 5.0 works, then there is not really a reason for changing the preferred version here. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [patchtest][PATCH 2/2] patchtest: fix linux-yocto version
On 6/13/19 4:29 PM, Adrian Bunk wrote: On Thu, Jun 13, 2019 at 03:46:04PM +0800, changqing...@windriver.com wrote: From: Changqing Li 4.9 is not avaiable currently, preferred version changed to 5.0, also correct the bbappend name 5.0 is already EOL upstream and will be removed soon. ... --- a/scripts/create-guest-machine +++ b/scripts/create-guest-machine @@ -145,10 +145,7 @@ cat >> $POKY/build/conf/auto.conf << EOF $PTSMARK MACHINE = "$MACHINE" -# The preferred kernel version in poky (4.10%, master) returns an error whilst -# executing patchtest on guest. Changing the preferred version to 4.9% as it -# is more suitable and does not present any errors. -PREFERRED_VERSION_linux-yocto_qemux86-64 = "4.9%" +PREFERRED_VERSION_linux-yocto_qemux86-64 = "5.0%" ... This looks as if it was a temporary workaround for some problem with kernel 4.10. If 5.0 works, then there is not really a reason for changing the preferred version here. Thanks, I will remove this line. cu Adrian -- BRs Sandy(Li Changqing) -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [patchtest][PATCH V2] patchtest: fix linux-yocto version
From: Changqing Li
4.9 is not avaiable currently, so remove version from bbappend
and remove PREFERRED_VERSION.
Signed-off-by: Changqing Li
---
.../linux/{linux-yocto_4.%.bbappend => linux-yocto_%.bbappend} | 0
scripts/create-guest-machine | 5 -
2 files changed, 5 deletions(-)
rename meta-patchtest/recipes-kernel/linux/{linux-yocto_4.%.bbappend =>
linux-yocto_%.bbappend} (100%)
diff --git a/meta-patchtest/recipes-kernel/linux/linux-yocto_4.%.bbappend
b/meta-patchtest/recipes-kernel/linux/linux-yocto_%.bbappend
similarity index 100%
rename from meta-patchtest/recipes-kernel/linux/linux-yocto_4.%.bbappend
rename to meta-patchtest/recipes-kernel/linux/linux-yocto_%.bbappend
diff --git a/scripts/create-guest-machine b/scripts/create-guest-machine
index 8dd6a2e..8381ef8 100755
--- a/scripts/create-guest-machine
+++ b/scripts/create-guest-machine
@@ -145,11 +145,6 @@ cat >> $POKY/build/conf/auto.conf << EOF
$PTSMARK
MACHINE = "$MACHINE"
-# The preferred kernel version in poky (4.10%, master) returns an error whilst
-# executing patchtest on guest. Changing the preferred version to 4.9% as it
-# is more suitable and does not present any errors.
-PREFERRED_VERSION_linux-yocto_qemux86-64 = "4.9%"
-
PACKAGE_CLASSES = "package_ipk"
IMAGE_FSTYPES = "ext4"
SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/dev/PATH";
--
2.7.4
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Download git source not the latest
I set up for my release version which is nothing to do with the git
source, how could I link the PV to autorev?
VERSION_MAJOR = "1"
VERSION_MINOR = "0"
VERSION_BUILD = "0"
PV = "${VERSION_MAJOR}.${VERSION_MINOR}.${VERSION_BUILD}"
Thanks Richard,
- jupiter
On 6/12/19, Richard Purdie wrote:
> On Tue, 2019-06-11 at 20:38 +1000, JH wrote:
>> Hi,
>>
>> I set up SRCREV = "${AUTOREV}" in the recipe of my application, but
>> too often it downloaded the old revision. How can I force the bitbake
>> to download the latest git source?
>
> What did you set PV to?
>
> You need to have SRCPV in PV for autorev to work properly.
>
> Regards,
>
> Richard
>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Command to make zimage to ramdisk format
Hi, I built the Yocto images: dev-image-20190528085324.rootfs.wic.gz zImage--.bin I need to build zImage to ramdisk to run it on RAM in development. What is the correct mkimage command can be used for add ramdisk to the zimage? $ mkimage -A arm -T ramdisk -C none -n uInitrd -d /path/to/initrd.img /path/to/uInitrd Thank you. Kind regards, - JH -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Command to make zimage to ramdisk format
Here is what you need (my best guess): https://lists.yoctoproject.org/pipermail/yocto/2018-July/041680.html Please, read carefully this thread. Zoran ___ On Thu, Jun 13, 2019 at 1:35 PM JH wrote: > > Hi, > > I built the Yocto images: > > dev-image-20190528085324.rootfs.wic.gz > zImage--.bin > > I need to build zImage to ramdisk to run it on RAM in development. > What is the correct mkimage command can be used for add ramdisk to the > zimage? > > $ mkimage -A arm -T ramdisk -C none -n uInitrd -d /path/to/initrd.img > /path/to/uInitrd > > Thank you. > > Kind regards, > > - JH > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] YP sstate example conf file
Hello, >From poky warrior tip, file meta-poky/conf/local.conf.sample """ # #SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH"; """ Should that be 2.7?? Or are you relying on the intelligence of the user to fix this up? If the former then it needs to go on a checklist. If the later then perhaps it would be better to use X.Y or something that does not appear to work. Some verbage to suggest the edit would probably be good as well. (and no, I did not run it like that. I'm slightly smarted than that.) https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-poky/conf/local.conf.sample?h=warrior#n235 Thanks, Bill William A. Mills Chief Technologist, Open Solutions, SDO Texas Instruments, Inc. 20450 Century Blvd Germantown MD 20878 240-643-0836 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] YP sstate example conf file
Good question. I've one related to this as well. It would be also good to document (if it isn't somewhere already) what builds populate this mirror. I assume it will be some autobuilder job with DISTRO = poky, but without file listing enabled over http I cannot even guess which MACHINEs were included. It would be useful to provide one tarball with all sigdata files, which could be manually downloaded to check what's available there and to debug why the sstate cache from this mirror wasn't reused in local build. Cheers, On Thu, Jun 13, 2019 at 4:32 PM William Mills wrote: > Hello, > > From poky warrior tip, file meta-poky/conf/local.conf.sample > """ > # > #SSTATE_MIRRORS ?= "file://.* > http://sstate.yoctoproject.org/2.5/PATH;downloadfilename=PATH"; > """ > > Should that be 2.7?? Or are you relying on the intelligence of the user > to fix this up? > > If the former then it needs to go on a checklist. > If the later then perhaps it would be better to use X.Y or something > that does not appear to work. Some verbage to suggest the edit would > probably be good as well. > > (and no, I did not run it like that. I'm slightly smarted than that.) > > > https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-poky/conf/local.conf.sample?h=warrior#n235 > > Thanks, > Bill > > > William A. Mills > Chief Technologist, Open Solutions, SDO > Texas Instruments, Inc. > 20450 Century Blvd > Germantown MD 20878 > 240-643-0836 > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [ptest-runner][PATCH] utils: ensure child can be session leader
From: Sakib Sajal
When running the run-execscript bash ptest as a user rather than root, a
warning:
bash: cannot set terminal process group (16036): Inappropriate ioctl for
device
bash: no job control in this shell
contaminates the bash log files causing the test to fail. This happens only
when run under ptest-runner and not when interactively testing!
The changes made to fix this include:
1. Get the process group id (pgid) before forking,
2. Set the pgid in both the parent and child to avoid a race,
3. Find, open and set permission on the child tty, and
4. Allow the child to attach to controlling tty.
Also add '-lutil' to Makefile. This lib is from libc and provides openpty.
Signed-off-by: Sakib Sajal
Signed-off-by: Randy MacLeod
---
Makefile | 2 +-
utils.c | 100 +--
2 files changed, 91 insertions(+), 11 deletions(-)
diff --git a/Makefile b/Makefile
index 1bde7be..439eb79 100644
--- a/Makefile
+++ b/Makefile
@@ -29,7 +29,7 @@ TEST_DATA=$(shell echo `pwd`/tests/data)
all: $(SOURCES) $(EXECUTABLE)
$(EXECUTABLE): $(OBJECTS)
- $(CC) $(LDFLAGS) $(OBJECTS) -o $@
+ $(CC) $(LDFLAGS) $(OBJECTS) -lutil -o $@
tests: $(TEST_SOURCES) $(TEST_EXECUTABLE)
diff --git a/utils.c b/utils.c
index ad737c2..d8977c6 100644
--- a/utils.c
+++ b/utils.c
@@ -1,5 +1,6 @@
/**
* Copyright (c) 2016 Intel Corporation
+ * Copyright (C) 2019 Wind River Systems, Inc.
*
* This program is free software; you can redistribute it and/or
* modify it under the terms of the GNU General Public License
@@ -22,23 +23,29 @@
*/
#define _GNU_SOURCE
+
#include
+#include
+#include
+#include
+#include
#include
-#include
#include
-#include
+#include
+#include
+#include
+#include
#include
-#include
+#include
+
+
+#include
#include
+#include
#include
#include
-#include
-#include
-#include
-#include
-#include
#include "ptest_list.h"
#include "utils.h"
@@ -346,6 +353,51 @@ wait_child(const char *ptest_dir, const char *run_ptest,
pid_t pid,
return status;
}
+/* get_slave_pty() returns an integer file descriptor.
+ * If it returns < 0, an error has occurred.
+ * Otherwise, it has returned the slave file descriptor.
+ * fp should be writable, likely stdout/err.
+ */
+static int
+setup_slave_pty(FILE *fp) {
+ int pty_master = -1;
+ int pty_slave = -1;
+ char pty_name[256];
+ struct group *gptr;
+ gid_t gid;
+ int slave = -1;
+
+ if (openpty(&pty_master, &pty_slave, pty_name, NULL, NULL) < 0) {
+ fprintf(fp, "ERROR: openpty() failed with: %s.\n",
strerror(errno));
+ return -1;
+ }
+
+ if ((gptr = getgrnam(pty_name)) != 0) {
+ gid = gptr->gr_gid;
+ } else {
+ /* If the tty group does not exist, don't change the
+* group on the slave pty, only the owner
+*/
+ gid = -1;
+ }
+
+ /* chown/chmod the corresponding pty, if possible.
+* This will only work if the process has root permissions.
+*/
+ if (chown(pty_name, getuid(), gid) != 0) {
+ fprintf(fp, "ERROR; chown() failed with: %s.\n",
strerror(errno));
+ }
+
+ /* Makes the slave read/writeable for the user. */
+ if (chmod(pty_name, S_IRUSR|S_IWUSR) != 0) {
+ fprintf(fp, "ERROR: chmod() failed with: %s.\n",
strerror(errno));
+ }
+
+ slave = open(pty_name, O_RDWR);
+ return (slave);
+}
+
+
int
run_ptests(struct ptest_list *head, const struct ptest_options opts,
const char *progname, FILE *fp, FILE *fp_stderr)
@@ -362,6 +414,8 @@ run_ptests(struct ptest_list *head, const struct
ptest_options opts,
int timeouted;
time_t sttime, entime;
int duration;
+ int slave;
+ int pgid = -1;
if (opts.xml_filename) {
xh = xml_create(ptest_list_length(head), opts.xml_filename);
@@ -379,7 +433,6 @@ run_ptests(struct ptest_list *head, const struct
ptest_options opts,
close(pipefd_stdout[1]);
break;
}
-
fprintf(fp, "START: %s\n", progname);
PTEST_LIST_ITERATE_START(head, p);
char *ptest_dir = strdup(p->run_ptest);
@@ -388,6 +441,13 @@ run_ptests(struct ptest_list *head, const struct
ptest_options opts,
break;
}
dirname(ptest_dir);
+ if (ioctl(0, TIOCNOTTY) == -1) {
+ fprintf(fp, "ERROR: Unable to detach from
controlling tty, %s\n", strerror(errno));
+ }
+
+ if ((pgid = getpgid(0)) == -1) {
+ fprintf(fp, "ERROR: getpgid() failed, %s\n",
strerror(errno));
+ }
child = fork();
Re: [yocto] [ptest-runner][PATCH] utils: ensure child can be session leader
On 6/13/19 6:39 PM, Randy MacLeod wrote: From: Sakib Sajal Oops. Sakib started on this and then had to work on something else so I finished it up. If needed, I'll send a v2 with me as the author, since "finishing up" was most of the work. We're both down as SOBs so whatever works. -- # Randy MacLeod # Wind River Linux -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] QA notification for completed autobuilder build (yocto-2.8_M1.rc2)
QA cycle report for 2.8 M1 RC2: 1. No high milestone defects. 2. Test results are available at following location: • For results of all automated tests, please refer to results at public AB [1] • For other test results, refer to git repo " yocto-testresults-contrib" [2] • For test report for test cases run by Intel and WR team, refer to git repo " yocto-testresults-contrib" [2] 3. 3 new defects are found in this cycle, BSP HW - parselog issue [3], BSP HW - audio issue [4], qemux86 oe-selftest failure on AB [5] 4. ptests failing in this release which were passing in previous release - acl [6]. 3 timeout issues observed in ptests - acl [7], bluez5 [8] and mdadm [9]. Richard's comments on ptest failures: There are three timeouts in ptest, acl, bluez5 (#13366) and mdadm (#13368). These are also not going to block the milestone release. The bluez5 issue is gcc9 related, mdadm was exposed by wider testing in master. The acl issue needs a bug opening and investigation as that is a regression. Summary of ptest in this build: qemuarm64-ptest: Total : 435597 Pass : 433344 Fail : 65 Skip : 2188 Timeout issues in bluez5 and mdadm qemux86-64-ptest Total : 45346 Pass : 43235 Fail : 56 Skip : 2055 Timeout issues in acl, bluez5 and mdadm 5. Summary of ltp test run in this build: qemuarm64-ltp Total : 1886 Pass : 1759 Fail : 127 qemux86-64-ltp Total : 1879 Pass : 1825 Fail : 54 === Links [1] - https://autobuilder.yocto.io/pub/releases/yocto-2.8_M1.rc2/testresults/ [2] - git clone g...@push.yoctoproject.org:yocto-testresults-contrib -b zeus [3] - [QA 2.8 M1 RC1][BSP HW] parselogs.ParseLogsTest.test_parselogs failure on coffeelake https://bugzilla.yoctoproject.org/show_bug.cgi?id=13396 [4] - [QA 2.8 M1 RC1][BSP HW] audio is not playing on coffeelake and nuc7 https://bugzilla.yoctoproject.org/show_bug.cgi?id=13397 [5] - [QA 2.8 M1 RC1] test_boot_machine_slirp is showing error for qemux86 https://bugzilla.yoctoproject.org/show_bug.cgi?id=13399 [6] - [QA 2.8 M1 RC1] acl ptest failure https://bugzilla.yoctoproject.org/show_bug.cgi?id=13395 [7] - acl ptest timeout due to perl update https://bugzilla.yoctoproject.org/show_bug.cgi?id=13391 [8] - bluez5 ptest hangs with gcc 9 https://bugzilla.yoctoproject.org/show_bug.cgi?id=13366 [9] - mdadm ptest times out https://bugzilla.yoctoproject.org/show_bug.cgi?id=13368 Thanks & Regards, Sangeeta Jain -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
