Workstation live x86_64 image https://kojipkgs.fedoraproject.org/compose/branched/Fedora-42-20250319.n.0/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-42-20250319.n.0.x86_64.iso from compose Fedora-42-20250319.n.0 is 2500216832 bytes, exceeding the maximum size 2500000000. Canonical maximum sizes can be found at https://docs.fedoraproject.org/en-US/releases/f42/spins/ and https://docs.fedoraproject.org/en-US/releases/f42/blocking/ . This check is run by the 'relval' tool, which has its own list of maximum sizes derived from those pages. If the maximum size used for this comparison is wrong, please add a comment and file a bug against relval at https://pagure.io/fedora-qa/relval/issues and it will be corrected. If you believe the canonical maximum size for an image should be changed, please follow the appropriate process before filing a relval bug.
Where are your newlines, you silly QA bot? Anyway, this is an automatic blocker per policy.
Notified the Workstation WG here: https://pagure.io/fedora-workstation/issue/477
The current nightly image is 2.23GB. https://koji.fedoraproject.org/koji/buildinfo?buildID=2684678 It probably got big temporarily because of the test to decrease the erofs chunk size. I reverted it when it didn't actually help so the size is back down now.
Yes, I already noticed, after creating the WG ticket :) -rw-r--r--. 1 qemu qemu 2500216832 Mar 21 10:07 Fedora-Workstation-Live-42-20250319.n.0.x86_64.iso -rw-r--r--. 1 qemu qemu 2396141568 Mar 24 07:54 Fedora-Workstation-Live-42-20250323.n.0.x86_64.iso Thanks.
yeah, I was tracking this but saw Neal's commits and assumed they had something to do with it, so I didn't escalate to the WG yet. I had it on my todo list today to check if current images were still oversize.
(In reply to Adam Williamson from comment #5) > yeah, I was tracking this but saw Neal's commits and assumed they had > something to do with it, so I didn't escalate to the WG yet. I had it on my > todo list today to check if current images were still oversize. Yeah, I reverted it because I noticed that it blew the images up and it didn't help the original issue at all.