On Mon Aug 17, 2026 at 4:48 PM CEST, Mathieu Dubois-Briand wrote:
> On Mon Aug 17, 2026 at 3:34 PM CEST, Sumanth Gavini wrote:
>> Hi Mathieu,
>>
>> Thanks for testing v15.
>>
>> The pkgconfig() errors are likely from old sstate packages built before
>> v15. Our change to package_rpm.bbclass invalidates do_package_write_rpm
>> sstate for all packages (the class code is part of the task hash), so a
>> clean build should regenerate all RPMs with consistent metadata and 
>> clear the errors.
>>
>> Could you trigger a clean build on the autobuilder without reusing
>> existing sstate? Also, if you can reproduce locally with a clean build,
>> that would help confirm whether the issue is the sstate transition or
>> something else in our fix.
>
> I can't really do a clean build without the sstate cache, sorry. Or at
> least not just by myself. Cleaning the cache on the autobuilder, will
> fix the build on the autobuilder, but not for any other user that will
> have the previous objects in the cache. So it means we could be breaking
> the build for some users.
>
> What I could do is, as for last week, forcefully increase PR on a bunch
> of recipes, to force a rebuild. This can be used to tests that
> everything works fine on the autobuilder when everything is rebuilt from
> scratch, but probably could bot be merged as-is.
>
> Weekly maintenance will happen soon, so I can't do that right now, but I
> will try to launch such a build tomorrow.
>
> Mathieu

Ok, so I finally managed to have a working build without sstate cache.

https://autobuilder.yoctoproject.org/valkyrie/#/builders/29/builds/4508

Some builds are still in progress, but we can probably already get some
conclusions:
- We do not see any installation issue. So the issues we had are
  probably related to the sstate cache in some way.
- We have one selftest failure, described below. I believe we already
  had that one with the previous iteration of this series.

2026-08-19 00:02:09,674 - oe-selftest - INFO - 
runtime_test.Postinst.test_failing_postinst (subunit.RemotedTestCase)
2026-08-19 00:02:09,681 - oe-selftest - INFO -  ... FAIL
...
2026-08-19 00:02:09,683 - oe-selftest - INFO - 5: 27/36 295/762 (7157.38s) (0 
failed) (runtime_test.Postinst.test_failing_postinst)
2026-08-19 00:02:09,683 - oe-selftest - INFO - 
testtools.testresult.real._StringException: Traceback (most recent call last):
  File 
"/srv/pokybuild/yocto-worker/oe-selftest-debian/build/layers/openembedded-core/meta/lib/oeqa/selftest/cases/runtime_test.py",
 line 409, in test_failing_postinst
    self.assertGreaterEqual(bb_result.output.find("Postinstall scriptlets of 
['postinst-rootfs-failing'] have failed."), 0,
    
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        "Warning about a failed scriptlet not found in bitbake output: %s" 
%(bb_result.output))
        
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.14/unittest/case.py", line 1315, in assertGreaterEqual
    self.fail(self._formatMessage(msg, standardMsg))
    ~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.14/unittest/case.py", line 750, in fail
    raise self.failureException(msg)
AssertionError: -1 not greater than or equal to 0 : Warning about a failed 
scriptlet not found in bitbake output: NOTE: Reconnecting to bitbake server...

https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/4599
https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/4425
https://autobuilder.yoctoproject.org/valkyrie/#/builders/23/builds/4649

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#243716): 
https://lists.openembedded.org/g/openembedded-core/message/243716
Mute This Topic: https://lists.openembedded.org/mt/120783174/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to