13323 2019-05-02 13:24:38 +0000 Add reproducibility automated testing 2019-09-05 14:45:49 +0000 1 1 10 QA/Testing Functional (self) Testing general unspecified x86 Multiple RESOLVED FIXED High enhancement 2.8 M3 13324 1 richard.purdie JPEWhacker alessioigorbogani JPEWhacker randy.macleod ross.burton --- --- No (bug/feature does not impact docs) oldest_to_newest 83686 0 richard.purdie 2019-05-02 13:24:38 +0000 We need to have tests that confirm our builds are reproducible. Initially we want a test which: a) runs a build in the usual way/location (can be sstate accelerated) b) changes to a new TMPDIR and rebuilds without using sstate c) compares the build in a) and b) and lists the differences both in packages themselves and in images. We'd start with a test for core-image-minimal, ultimately moving to more complex images such as sato-sdk and perhaps world builds. 84488 1 ross.burton 2019-07-25 14:42:10 +0000 The test suite is merged in oe-core now but is skipped currently. We can close this when the test is enabled. 84506 2 ross.burton 2019-07-25 15:19:26 +0000 With a couple of patches I'm about to send, the current failure list is: The following deb packages are missing or different: ca-certificates_20190110-r0_all.deb libical-dbg_2.0.0-r0_amd64.deb libical_2.0.0-r0_amd64.deb perl-ptest_5.30.0-r0_amd64.deb systemd-dbg_242+0+db2e367bfc-r0_amd64.deb systemd_242+0+db2e367bfc-r0_amd64.deb kernel-image-bzimage-5.0.19-yocto-standard_5.0.19+git0+c2e34d9ab2_00638cdd8f-r0_amd64.deb 84510 3 ross.burton 2019-07-25 17:54:11 +0000 So if the test uses reproducible_build_simple instead of the convoluted magic in the normal class, more recipes are reproducible. With that change it's just: libical-dbg_2.0.0-r0_amd64.deb libical_2.0.0-r0_amd64.deb systemd-dbg_242+0+db2e367bfc-r0_amd64.deb systemd_242+0+db2e367bfc-r0_amd64.deb kernel-image-bzimage-5.0.19-yocto-standard_5.0.19+git0+c2e34d9ab2_00638cdd8f-r0_amd64.deb The libical one is build paths in the cmake files, iirc. 84518 4 ross.burton 2019-07-26 10:34:42 +0000 ical hopefully fixed with v3 of the upgrade. systemd is because it embeds the build timestamp as a build epoch. 84537 5 ross.burton 2019-07-26 20:46:32 +0000 With a bit of a hack to fix systemd, and a little patch to the kernel, I have the test passing here. 84576 6 ross.burton 2019-08-02 10:19:45 +0000 For a laugh I changed the QA test to build core-image-sato instead of -minimal. gstreamer1.0-libav-dbg_1.16.0-r0_amd64.deb gstreamer1.0-libav_1.16.0-r0_amd64.deb jpeg-tools_2.0.2-r0_amd64.deb libatk-1.0-doc_2.32.0-r0_amd64.deb libatspi-src_2.32.1-r0_amd64.deb libical-dbg_3.0.5-r0_amd64.deb libical_3.0.5-r0_amd64.deb libjpeg-dbg_2.0.2-r0_amd64.deb libjpeg62_2.0.2-r0_amd64.deb librsvg-2-2_2.40.20-r0_amd64.deb librsvg-2-dbg_2.40.20-r0_amd64.deb libsoup-2.4-doc_2.66.2-r0_amd64.deb libtag-c0_1.11.1-r0_amd64.deb libtag-dbg_1.11.1-r0_amd64.deb libturbojpeg0_2.0.2-r0_amd64.deb pango-src_1.42.4-r0_amd64.deb xserver-xorg-src_1.20.4-r0_amd64.deb The ones which impact *just* the -src are where absolute build paths are embedded in generated sources, I've a fix for xserver-xorg already. 84759 7 JPEWhacker 2019-08-27 19:37:20 +0000 This patch series is the initial attempt to enable the reproducible OEQA test for core-image-minimal: http://lists.openembedded.org/pipermail/openembedded-core/2019-August/286154.html 84883 8 JPEWhacker 2019-09-05 14:45:49 +0000 The autobuilder is now running the reproducible build test.