On 2020-11-12 21:28, Petter Reinholdtsen wrote:
[Gunnar Hjalmarsson]Additional observations:* The testing failure in Ubuntu started around October 31. * The test-command-line script fails on amd64 and i386 but succeeds on other architectures.Is it possible to 'diff' the logs from a successful and a failing test, to see what changed? Perhaps a new version of some package or something? I get the following when running in my Sid chroot: isenkram-lookup (process:10498): GLib-GObject-CRITICAL (recursed) **: g_object_get_qdata: assertion 'G_IS_OBJECT (object)' failedAborted No idea what it mean. :)
Unfortunately I don't have the knowledge to help with the analysis. But yes, since isenkram hasn't changed recently, the explanation ought to be changes in some other package(s).
Anyway, I attached two logs from test runs in Ubuntu's autopkgtest which passed. One is on amd64 from October 29 and one is on arm64 from yesterday. They both show a bunch of warning messages, but lack the "KeyError" from a recent amd64 test run (attached in my last message).
-- Gunnar Hjalmarsson https://launchpad.net/~gunnarhj
test-command-line-stdout_success_amd64_20201029.gz
Description: application/gzip
test-command-line-stdout_success_arm64_20201111.gz
Description: application/gzip
