A couple of the autopkgtests marked 'regression' don't appear to be indicative of true regressions -
1. apparmor/firejail/jammy/s390x https://autopkgtest.ubuntu.com/packages/f/firejail/jammy/s390x https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/f/firejail/20251014_154207_c54b0@/log.gz Failing due to a missing dependency (depends on firefox, but firefox isn't available for jammy/s390x) - entire history of tests in this queue seem to be failing for the same reason. 1009s The following packages have unmet dependencies: 1009s satisfy:command-line : Depends: firefox but it is not installable 1009s E: Unable to correct problems, you have held broken packages. https://packages.ubuntu.com/jammy/firefox - not available for jammy/s390x 2. apparmor/dbug-broker/noble/s390x https://autopkgtest.ubuntu.com/packages/d/dbus-broker/noble/s390x Two different failure causes have been observed here - a. https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/d/dbus-broker/20251022_163451_3e47f@/log.gz VM's clock was behind the source files' timestamps. This was observed only once, on the most recent failure. 103s ERROR: Clock skew detected. File /tmp/autopkgtest.Fjq5ev/build.n3V/src/obj-s390x-linux-gnu/../meson.build has a time stamp 58.6022s in the future. b. https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/s390x/d/dbus-broker/20251014_134942_c3e7c@/log.gz On all other re-runs of this, compilation of test executables fails due to 'DEBUGINFOD_URLS' not being defined. The number of test executables which fail to compile due to this varies (i.e., it is not consistently the same N test executables failing to compile due to this on each re- run, which is confusing). This seems to align with cause of historical failures in the queue (though there are eventual passes). 244s cc: fatal error: environment variable ‘DEBUGINFOD_URLS’ not defined --- (1) seems like it should be resolved with a bad-test hint or made passing with a migration-reference/0 run. (2) also seems very unlikely to be related to any of the apparmor changes being tested, though I am unsure of the root cause or what the solution should be to unblock this SRU. Any thoughts or recommendations for next steps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2115234 Title: Improper globbing in rules for /sys/devices PCI paths To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2115234/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
