4 ms·

Actual numbers for bullseye currently look like this: https://debian.notset.fr/rebuild/results/bullseye_full.amd64%2Ball.png https://debian.notset.fr/rebuild/r

by kpcyrd 5y ago

Actual numbers for bullseye currently look like this: https://debian.notset.fr/rebuild/results/bullseye_full.amd64%2Ball.png https://debian.notset.fr/rebuild/results/bullseye_full.amd64...

dane-pgp 5y ago
Why are 28.8% of Debian stable packages currently "pending"? The stats on reproducible-builds.org say that "29595 packages (95.7%) successfully built reproducibly in bullseye/amd64."[0] which may not be accurate for the reasons given in the grandparent post, but I note that the situation seems to have improved significantly[1] since that mailing list thread. [0] https://tests.reproducible-builds.org/debian/bullseye/index_suite_amd64_stats.html https://tests.reproducible-builds.org/debian/bullseye/index_... [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900837#17 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900837#17
- Foxboron 5y ago
  >Why are 28.8% of Debian stable packages currently "pending"? They are separate systems. The CI/CD and the rebuilder are not doing the same job essentially. The 28.8% on pending might be because of slow rebuild times as the integration system has had more time building packages with significantly more CPU power behind it.
  - dane-pgp 5y ago
    I guess the release date was as recent as 2021-07-23, and it's conceivable that such a rebuilding project being run only with spare CPU cycles might take months (or might only have started recently). As an interesting data point, I see that the number of pending packages is now 21.2%. Let's hope that most of these remaining packages (and those being retried) turn out to be reproducible.
    - Foxboron 5y ago
      Such rebuilds systems are complicated and might not work 100% when you first start out. There can be multiple complete rebuilds done while removing edge-case bugs that either fails the building or introduces variance into the builds.
      - dane-pgp 5y ago
        That's some helpful context, thank you. As a further analysis, I note that, excluding the current "pending" builds, the "reproducible" segment accounts for 93% of all packages so far. I don't know if it's reasonable to assume that the "pending" packages are a representative sample in terms of their reproducibility, or how likely the "retry" packages are to succeed, but I'm hopeful that in a few days the "reproducible" stat will pass 90% for real.
        dane-pgp 5y ago
        As predicted, the "reproducible" segment on that pie chart[0] is now at 90.1% with a few percent of packages still pending or being retried. [0] https://debian.notset.fr/rebuild/results/bullseye_full.amd64%2Ball.png https://debian.notset.fr/rebuild/results/bullseye_full.amd64...

by kpcyrd 5y ago

Actual numbers for bullseye currently look like this: https://debian.notset.fr/rebuild/results/bullseye_full.amd64%2Ball.png https://debian.notset.fr/rebuild/results/bullseye_full.amd64...

dane-pgp 5y ago

Why are 28.8% of Debian stable packages currently "pending"? The stats on reproducible-builds.org say that "29595 packages (95.7%) successfully built reproducibly in bullseye/amd64."[0] which may not be accurate for the reasons given in the grandparent post, but I note that the situation seems to have improved significantly[1] since that mailing list thread. [0] https://tests.reproducible-builds.org/debian/bullseye/index_suite_amd64_stats.html https://tests.reproducible-builds.org/debian/bullseye/index_... [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900837#17 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900837#17

Foxboron 5y ago
>Why are 28.8% of Debian stable packages currently "pending"? They are separate systems. The CI/CD and the rebuilder are not doing the same job essentially. The 28.8% on pending might be because of slow rebuild times as the integration system has had more time building packages with significantly more CPU power behind it.
- dane-pgp 5y ago
  I guess the release date was as recent as 2021-07-23, and it's conceivable that such a rebuilding project being run only with spare CPU cycles might take months (or might only have started recently). As an interesting data point, I see that the number of pending packages is now 21.2%. Let's hope that most of these remaining packages (and those being retried) turn out to be reproducible.
  - Foxboron 5y ago
    Such rebuilds systems are complicated and might not work 100% when you first start out. There can be multiple complete rebuilds done while removing edge-case bugs that either fails the building or introduces variance into the builds.
    - dane-pgp 5y ago
      That's some helpful context, thank you. As a further analysis, I note that, excluding the current "pending" builds, the "reproducible" segment accounts for 93% of all packages so far. I don't know if it's reasonable to assume that the "pending" packages are a representative sample in terms of their reproducibility, or how likely the "retry" packages are to succeed, but I'm hopeful that in a few days the "reproducible" stat will pass 90% for real.
      - dane-pgp 5y ago
        As predicted, the "reproducible" segment on that pie chart[0] is now at 90.1% with a few percent of packages still pending or being retried. [0] https://debian.notset.fr/rebuild/results/bullseye_full.amd64%2Ball.png https://debian.notset.fr/rebuild/results/bullseye_full.amd64...