On Mon, May 4, 2020 at 8:56 AM Bruce Ashfield via lists.openembedded.org <bruce.ashfield=gmail....@lists.openembedded.org> wrote: > > On Mon, May 4, 2020 at 4:31 AM Richard Purdie > <richard.pur...@linuxfoundation.org> wrote: > > > > Hi Bruce, > > > > On Sun, 2020-05-03 at 11:44 -0400, bruce.ashfi...@gmail.com wrote: > > > From: Bruce Ashfield <bruce.ashfi...@gmail.com> > > > > > > Hi all, > > > > > > Here are the -stable updates I've collected since m3 of dunfell. I > > > ran things through the autobuilder, and no new kernel issues were > > > picked up. > > > > > > The -dev bump is good for master, while all of the 5.4-stable bumps > > > are good for both master and dunfell. > > > > I pulled these into master-next and saw reproducibility issues. I > > wondered why your test build didn't show it, turns out it also did: > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/1024 > > > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - > > ====================================================================== > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - FAIL: > > reproducible.ReproducibleTests.test_reproducible_builds > > (subunit.RemotedTestCase) > > 2020-05-04 05:18:46,863 - oe-selftest - INFO - > > ---------------------------------------------------------------------- > > 2020-05-04 05:18:46,864 - oe-selftest - INFO - > > testtools.testresult.real._StringException: > > > > AssertionError: The following deb packages are missing or different: > > /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/deb/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_amd64.deb > > The following ipk packages are missing or different: > > /home/pokybuild/yocto-worker/oe-selftest-centos/build/build-st-36044/reproducibleB/tmp/deploy/ipk/./qemux86_64/kernel-module-kheaders-5.4.38-yocto-standard_5.4.38+git0+f405543442_6cb5b11e83-r0_qemux86_64.ipk > > > > I don't see any changes in the kernels that would have triggered it, > but they never are obvious.
I am working on some kernel reproducibility changes that were discussed about three weeks ago. Is the default for reproducible builds in master-next different from what it was before dunfell was releases ? If so, that might explain why I'm not seeing a change that would have triggered it (i.e. this is unrelated to my -stable changes). Like I was mentioning before, if there's a document or pastebin of steps I can follow, I can run the tests against my pending changes and finish them for master. They of course would not necessarily be suitable for dunfell. Bruce > > I unfortunately have no idea how to run reproducibility tests on the > kernels locally and my build server at home is brutally underpowered > for more than one core-image build per arch a day (hence the > autobuilder runs). > > Is there a cut and paste se of instructions about the tests that I > could follow ? > > Bruce > > > master-next was: > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/900 > > > > and friends. > > > > Cheers, > > > > Richard > > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II > -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#137821): https://lists.openembedded.org/g/openembedded-core/message/137821 Mute This Topic: https://lists.openembedded.org/mt/73956229/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/leave/8023207/1426099254/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
