build fails on Ubuntu Jammy 22.04 - failing tests

Bug #2018517 reported by Valentijn Sessink
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2-unsigned (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Several tests fail when building on a freshly installed Ubuntu 22.04.

Trying to compile 2.06-2ubuntu7:
- btrfs_test fails because it complains that "invalid sectorsize 256, expected range is [4K, 64K]", although trying to use 4K - 64K gives a new error, "sectorsize 8192 not yet supported for page size 4096". I was able to get the build going with MINLOGSECSIZE=12, MAXLOGSECSIZE=12, but that's probably silly. Also, I'm not sure what happens on a Linux system with page size <> 4K (would mkbtrfs complain about a sector size 4K there?)
- fat_test fails because grub-fs-tester contains "GRUBTEST ;_" for a label and mkfs.vfat complains "Labels with characters *?.,;:/\|+=<>[]" are not allowed". (Setting the label to "GRUBTEST _" fixes this.

squashfs_test shows a "TIME FAIL" - removing "-not-reproducable" as 2.06-2ubuntu14 does, did not help.

Please note: trying to compile 2.06-2ubuntu16 gave even more failed tests: xfs_test, ahci_test and grub_func_test failed, too, but as 2.06-2ubuntu16 has no business on 22.04, I didn't investigate further.

Anyway: changing "MINLOGSECSIZE=8" to "12" for btrfs*, and changing the FSLABEL to "GRUBTEST _" for vfat, fixed the btrfs_test and vfat_test for me. Squashfs still shows a TIME FAIL.

description: updated
Revision history for this message
Julian Andres Klode (juliank) wrote :

The current version for 22.04 is 2.06-2ubuntu14.2 and it built successfully on the builders. There can be a lot of reasons why the test suite fails on a local machine, for example, the file system tests fail when running as root in a container.

We can't fix the test suite everywhere - ultimately what matters is that it works on the builders, which it does.

Changed in grub2-unsigned (Ubuntu):
status: New → Won't Fix
status: Won't Fix → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.