Public bug reported: When looking for SRUs we found that since end of April all systemd tests on amd64 in resolute seem to fail.
They all seem to hit this: 3299s Processing triggers for procps (2:4.0.4-9ubuntu1) ... 3299s ‣ Copying in extra file trees… 3303s ‣ Running postinstall script /tmp/autopkgtest.sQhbLx/build.NaA/src/mkosi/mkosi.postinst.chroot… 3303s jq: parse error: Invalid numeric literal at EOF at line 1, column 16384 3303s ‣ "/work/postinst final" returned non-zero exit code 5. 3304s + cleanup We compare one of the recent fails https://autopkgtest.ubuntu.com/results/autopkgtest-resolute/resolute/amd64/s/systemd/20260603_005223_92eac@/log.gz With the last good run https://autopkgtest.ubuntu.com/results/autopkgtest-resolute/resolute/amd64/s/systemd/20260420_173427_28792@/log.gz And we found that there is a difference that might be related: Good: 2125s Get:159 http://archive.ubuntu.com/ubuntu resolute/main amd64 jq amd64 1.8.1-4ubuntu1 [72.4 kB] Bad 3196s Get:159 http://archive.ubuntu.com/ubuntu resolute-updates/main amd64 jq amd64 1.8.1-4ubuntu2 [72.4 kB] So this might (tm) be a regression by the jq security update in https://launchpad.net/ubuntu/+source/jq/1.8.1-4ubuntu2 or that is a red herring. I do not know. We could migration-reference/0 it I guess, but we wanted to know if you are aware, have a plan, or any other thing that would say please do not reset expectations on this one. ** Affects: jq (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: jq (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2155132 Title: systemd upstream test falling apart in resolute (maybe due to jq) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jq/+bug/2155132/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
