Comment 19 for bug 2050017

Revision history for this message
Andreas Hasenack (ahasenack) wrote (last edit ):

> (I'm curious about the autopkgtest results.)

They passed for amd64 already:
Results: (from http://autopkgtest.ubuntu.com/results/autopkgtest-noble-ahasenack-apache2-modssl-provider-support/?format=plain)
  apache2 @ amd64:
    06.03.24 17:05:50 Log 🗒️ ✅ Triggers: apache2/2.4.58-1ubuntu4~ppa1

log: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-ahasenack-apache2-modssl-provider-support/noble/amd64/a/apache2/20240306_170550_0cb4e@/log.gz

but failed for s390x all over the place:
  apache2 @ s390x:
    06.03.24 17:54:30 Log 🗒️ ❌ Triggers: apache2/2.4.58-1ubuntu4~ppa1
      1617s run-test-suite FAIL 🟥
      1617s duplicate-module-load FAIL 🟥
      1617s default-mods FAIL 🟥
      1617s htcacheclean FAIL 🟥
      1617s ssl-passphrase FAIL 🟥
      1617s check-http2 FAIL 🟥
      1617s check-ubuntu-branding FAIL 🟥
      1617s chroot FAIL 🟥

Log: https://autopkgtest.ubuntu.com/results/autopkgtest-noble-ahasenack-apache2-modssl-provider-support/noble/s390x/a/apache2/20240306_175430_7cb94@/log.gz

It's a dependency problem while installing packages. The archive is still in a lot of flux due to the time_t 64bit changes, which mean a lot of rebuilds. I'll retry later.