Verification Builds and Snapshots For Debian

[Vagrant Cascadian]

On 2023-09-19, Vagrant Cascadian wrote:
> * Some actual results!
>
> Testing only arch:all and arch:amd64 .buildinfos, I had decent luck with
> 2023/09/16:
>
> total buildinfos to check: 538
> attempted/building: 535
>
> unreproducible: 28      5 %
> reproducible:   461     85 %
> failed:         46      8 %
> unknown:        3       0 %
...
> I also had similar results for 2023-09-15 and 2023-09-17, but ... this
> morning most of those results myseriously disappeared!?! No idea what
> happened to them.

It was nagging at me, so I re-ran the builds for those days, and it was
not too bad, and looks similar to the initial results ... from memory:

2023/09/15
total buildinfos to check: 151
attempted/building: 151
unreproducible: 34      22 %
reproducible:   97      64 %
failed:         20      13 %
unknown:        0       0 %

2023/09/17
total buildinfos to check: 152
attempted/building: 149
unreproducible: 10      6 %
reproducible:   125     82 %
failed:         14      9 %
unknown:        3       1 %

Or, for all three days 2023-09-15 to 2023-09-17 combined:

total buildinfos to check: 839
attempted/building: 835
unreproducible: 72      8 %
reproducible:   683     81 %
failed:         80      9 %
unknown:        4       0 %

Still not bad for real-world testing.


Also, my test environments unintentionally introduced a few more
variations, for example:

+Build-Tainted-By:
+ merged-usr-via-aliased-dirs

The thorn in Debian's side strikes again. The tarballs I was using were
usrmerge, but the buildds are still not doing usrmerge. This is more
fiddly to set up a non-usrmerge base tarball than it used to be, but it
is doable, and at least the .buildinfo records this information.


Mysterious discrepancies in dependency differences:

  libfontconfig-dev (= 2.14.2-6),
  libfontconfig1 (= 2.14.2-6),
- libfontconfig1-dev (= 2.14.2-6),

Apparently libfontconfig-dev provides libfontconfig1-dev, and
libfontconfig1-dev is a transitional package, and sometimes
dpkg-genbuildinfo decides to include it explicitly and... sometimes not?
I do not think this particular case is likely to change the build
results, at least.


 Environment:
- DEB_BUILD_OPTIONS="parallel=6"
+ DEB_BUILD_OPTIONS="parallel=7"
+ LANG="C.UTF-8"
  LC_ALL="C.UTF-8"

Could have set up the builds to use the same level of parallelism easily
enough.

LANG was trickier. Some of the buildd .buildinfo files explicitly set
LANG="C.UTF-8" but some have it undefined. If I left it unset, it ended
up using LANG="en_US.UTF-8".  I chose to consistently use LANG="C.UTF-8"
in my testing.  Although I am not even entirely sure C.UTF-8 is a valid
value for LANG...


live well,
  vagrant
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://lists.reproducible-builds.org/pipermail/rb-general/attachments/20230920/40d0ec4e/attachment.sig>