Comment 15 for bug 1944037

Revision history for this message
Paride Legovini (paride) wrote (last edit ):

I verified more in-depth that we can actually sync liburing instead of merging.

# Builds

The package builds fine everywhere we care of. Build logs:

 * amd64: https://launchpadlibrarian.net/569586848/buildlog_ubuntu-jammy-amd64.liburing_2.1-2_BUILDING.txt.gz
 * arm64: https://launchpadlibrarian.net/569586917/buildlog_ubuntu-jammy-arm64.liburing_2.1-2_BUILDING.txt.gz
 * armhf: https://launchpadlibrarian.net/570371687/buildlog_ubuntu-jammy-armhf.liburing_2.1-2_BUILDING.txt.gz
 * ppc64el: https://launchpadlibrarian.net/569586810/buildlog_ubuntu-jammy-ppc64el.liburing_2.1-2_BUILDING.txt.gz
 * https://launchpadlibrarian.net/569586770/buildlog_ubuntu-jammy-s390x.liburing_2.1-2_BUILDING.txt.gz

These are builds done with -proposed enabled in the PPA.

# Autopkgtests

They pass on all the build architectures:

 * amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-paride-liburing-2.1-2/jammy/amd64/libu/liburing/20211123_104250_b8456@/log.gz
 * arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-paride-liburing-2.1-2/jammy/arm64/libu/liburing/20211123_103949_bbc86@/log.gz
 * armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-paride-liburing-2.1-2/jammy/armhf/libu/liburing/20211123_122952_18c52@/log.gz
 * ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-paride-liburing-2.1-2/jammy/ppc64el/libu/liburing/20211123_104609_ff750@/log.gz
 * s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-paride-liburing-2.1-2/jammy/s390x/libu/liburing/20211123_104028_be566@/log.gz

Note: all but the armhf one pass with:

@@@@@@@@@@@@@@@@@@@@ summary
test-build PASS
test-unit PASS

while the liburing 0.7-3ubuntu3 runs have runs like:

autopkgtest [04:17:21]: @@@@@@@@@@@@@@@@@@@@ summary
test-build PASS
test-unit FLAKY non-zero exit status 2

where the overall run passes but with ignored failures (d/t/control has `Restrictions: flaky skippable`).

The armhf autopkgtest has Segmentation faults in test-build, but the test overall passes as it's `Restrictions: flaky`. Apparently here's no baseline armhf Jammy autopkgtest run for liburing (https://autopkgtest.ubuntu.com/packages/liburing), so this doesn't really count as a regression (still not nice).

## Skipped tests (amd64)

The test run for the version currently in Jammy [1] skips two tests:

---------------
Unable to map a huge page. Try increasing /proc/sys/vm/nr_hugepages by at least 1.
Skipping the hugepage test
Not enough memory for this test, skipping

Running test fc2a85cb02ef-test:
Test needs failslab/fail_futex/fail_page_alloc enabled, skipped
---------------

The same skips are in the autopkgtest run from the PPA (i.e. from the hereby proposed sync). There are other tests skipped in the PPA autopkgtest run, but those are outright (ignored) failures in the liburing 0.7-3ubuntu3 autopkgtest run.

The PPA autopkgtest run has some tests skipped because of missing root permissions. Those pass locally in a run done with `autopkgtest --user root ... -- qemu`.

[1] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/libu/liburing/20210714_041738_a5a0a@/log.gz