unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Thiago Jung Bauermann via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 56625@debbugs.gnu.org
Subject: bug#56625: [core-updates] libaio test fails on powerpc64le-linux due to kernel bug
Date: Sun, 17 Jul 2022 22:22:17 -0300	[thread overview]
Message-ID: <87r12jyzbz.fsf@kolabnow.com> (raw)


On the core-updates branch, libaio has been updated to version 0.3.113.
This version contains a new test which fails on guixp9 (one of the
powerpc64le-linux builders) due to a bug present in the kernel it is
running:

--8<---------------cut here---------------start------------->8---
Starting cases/23.p
FAIL: poll missed an event!
FAIL: poll missed an event!
FAIL: poll missed an event!
test cases/23.t completed FAILED.
Completed cases/23.p with 1 -- FAILED.
Pass: 18  Fail: 1  Skip: 0
Test run complete at Sun Jul 17 10:39:33 AM UTC 2022
make[1]: *** [Makefile:53: partcheck] Error 1
make[1]: Leaving directory '/tmp/guix-build-libaio-0.3.113.drv-0/libaio-0.3.113/harness'
make: *** [Makefile:23: partcheck] Error 2

Test suite failed, dumping logs.
error: in phase 'check': uncaught exception:
%exception #<&invoke-error program: "make" arguments: ("partcheck" "-j" "8" "prefix=/gnu/store/igbnjwlfr0mim89if6z46cqba0ny5lww-libaio-0.3.113" "CC=gcc") exit-status: 2 term-signal: #f stop-signal: #f>
phase `check' failed after 97.9 seconds
command "make" "partcheck" "-j" "8" "prefix=/gnu/store/igbnjwlfr0mim89if6z46cqba0ny5lww-libaio-0.3.113" "CC=gcc" failed with status 2
--8<---------------cut here---------------end--------------->8---

The header of libaio/harness/cases/23.t says:

 * Verify that aio poll doesn't miss any events.  This is a regression test for
 * kernel commit 363bee27e258 ("aio: keep poll requests on waitqueue until
 * completed")¹.

guixp9 is running kernel linux-image-5.10.0-0.bpo.8-powerpc64le version
5.10.46-4~bpo10+1. The kernel commit mentioned above was backported to
upstream stable kernel 5.10.85, which was included in Debian's
linux-image version 5.10.92-1, available in the buster-backports kernel.

So long story short, we need to update guixp9's kernel so that we can
build core-update's libaio. I suggest we take the opportunity to update
all of the Debian packages as well.

I don't have access to guixp9's console, so unfortunately I can't
perform the update. Or rather, I can if someone else reboots the machine
afterwards and fixes any boot issues that could come up (hopefully not
but it's always a possibility).

-- 
Thanks
Thiago




             reply	other threads:[~2022-07-18  1:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18  1:22 Thiago Jung Bauermann via Bug reports for GNU Guix [this message]
2023-05-04 14:25 ` bug#56625: [core-updates] libaio test fails on powerpc64le-linux due to kernel bug Christopher Baines

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r12jyzbz.fsf@kolabnow.com \
    --to=bug-guix@gnu.org \
    --cc=56625@debbugs.gnu.org \
    --cc=bauermann@kolabnow.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).