Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 46968C5B549 for ; Thu, 5 Jun 2025 00:13:27 +0000 (UTC) Received: from fllvem-ot04.ext.ti.com (fllvem-ot04.ext.ti.com [198.47.19.246]) by mx.groups.io with SMTP id smtpd.web10.32295.1749082398172728863 for ; Wed, 04 Jun 2025 17:13:18 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=maDWIe1L; spf=pass (domain: ti.com, ip: 198.47.19.246, mailfrom: rs@ti.com) Received: from fllvem-sh03.itg.ti.com ([10.64.41.86]) by fllvem-ot04.ext.ti.com (8.15.2/8.15.2) with ESMTP id 5550CuwY3949404; Wed, 4 Jun 2025 19:12:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1749082376; bh=W2tCLGruXri+YUJOjhZWw0MxUeer0SYQ4cy3pXSPeQg=; h=Date:CC:Subject:From:To:References:In-Reply-To; b=maDWIe1L2JXNOQ81Ga6sn5EgeQsnIEt1DuB/AAjQsHZxqYuu8tMdQ+bMNO7gE183T zQtGragWuKlT9pukUFl42t7LSaxv6j6w63TRrnTujUENdQYGQzO5RNxaFVhN2qWZgN 1GySDU/oyxohoa8ggfucrFK14yWUc4QVu7rklX6A= Received: from DLEE115.ent.ti.com (dlee115.ent.ti.com [157.170.170.26]) by fllvem-sh03.itg.ti.com (8.18.1/8.18.1) with ESMTPS id 5550CuPC421869 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA256 bits=128 verify=FAIL); Wed, 4 Jun 2025 19:12:56 -0500 Received: from DLEE108.ent.ti.com (157.170.170.38) by DLEE115.ent.ti.com (157.170.170.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Wed, 4 Jun 2025 19:12:55 -0500 Received: from lelvem-mr05.itg.ti.com (10.180.75.9) by DLEE108.ent.ti.com (157.170.170.38) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Wed, 4 Jun 2025 19:12:55 -0500 Received: from localhost (rs-desk.dhcp.ti.com [128.247.81.144]) by lelvem-mr05.itg.ti.com (8.18.1/8.18.1) with ESMTP id 5550CtMd2846901; Wed, 4 Jun 2025 19:12:55 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Date: Wed, 4 Jun 2025 19:12:55 -0500 Message-ID: CC: , Subject: Re: [oe-core][PATCHv6 0/5] Display manager proposal for x11 and wayland From: Randolph Sapp To: Mathieu Dubois-Briand , , , , , , , , , X-Mailer: aerc 0.20.1-0-g2ecb8770224a References: <20250520233935.740242-1-rs@ti.com> In-Reply-To: X-C2ProcessedOrg: 333ef613-75bf-4e12-a4b1-8e3623f5dcea List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Thu, 05 Jun 2025 00:13:27 -0000 X-Groupsio-URL: https://lists.openembedded.org/g/openembedded-core/message/217971 On Wed May 28, 2025 at 6:53 AM CDT, Mathieu Dubois-Briand wrote: > On Wed May 28, 2025 at 12:16 AM CEST, Randolph Sapp wrote: [snip] >> Ah, the auth failures persist. Normally this is caused when the user att= empts to >> login before the user account was created or something unusual like that= . I >> don't suppose there's any way this could be happening on the test machin= es? >> >> I'm not able to reproduce this locally, but my build config is different= . I tend >> to use oe-core and nodistro instead of poky. They aren't playing around = with the >> reproducible build date stuff or anything like that are they? >> >> Well, I mean I did see this on occasion. The first login attempt almost = always >> failed, but the subsequent attempts were fine. Bumping the attempt count= back up >> the default (2) was enough to resolve it on my end, but evidently it's n= ot >> enough here. >> >> This is not happening on hardware from what I'm seeing. > > Hi Randolph, > > I was able to reproduce it locally, with the following configuration: > - https://git.yoctoproject.org/poky-ci-archive on tag > autobuilder.yoctoproject.org/valkyrie/a-full-1630. > - template local.conf, with the following modifications: > MACHINE =3D "qemux86" > DISTRO =3D "poky-altcfg" > SDKMACHINE =3D "x86_64" > PACKAGE_CLASSES =3D "package_rpm package_deb package_ipk" > INHERIT +=3D 'image-buildinfo' > IMAGE_BUILDINFO_VARS:append =3D ' IMAGE_BASENAME IMAGE_NAME' > PACKAGE_CLASSES =3D 'package_ipk package_rpm package_deb' > IMAGE_ROOTFS_EXTRA_SPACE:append =3D '${@bb.utils.contains('IMAGE_FEATUR= ES', 'package-management', ' + 262144', '', d)}' > IMAGE_INSTALL:append =3D ' ssh-pregen-hostkeys' > SANITY_TESTED_DISTROS =3D '' > OE_FRAGMENTS +=3D 'core/yocto-autobuilder/autobuilder core/yocto-autobu= ilder/autobuilder-resource-constraints' > # (Plus my own sstate cache and downloads dir). > - bitbake core-image-sato > - bitbake core-image-sato:do_testimage > > Of course using the tag from poky-ci-archive is not mandatory, you > should see the same behaviour with master branch and your patches. > > I saw some oe-selftest was also failing on the autobuilder, with an > error related to emptty. You can reproduce it with: > > oe-selftest -r sstatetests.SStateHashSameSigs3.test_sstate_sametune_sames= igs Status report, since it's been a little bit. Seems this some i386/x86 fault only exposed in this specific environment. I= was unable to reproduce it on Archlinux32. I've traced it back to a SEGFAULT wh= en we attempt to execute mcookie as the target user. Odd stuff. Delve and gdb are= n't helping me here. Running some more tests to see if I can corner this some o= ther way. - Randolph