Your message dated Tue, 5 Mar 2024 17:38:15 +0200
with message-id <Zec8Z7p5eVdHAUJ3@localhost>
and subject line Re: Bug#1057717: cmake ftbfs on ppc64el (and ppc64)
has caused the Debian Bug report #1057717,
regarding libuv1: io_uring support randomly segfaults after signal on 
ppc64el/ppc64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1057717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cmake
Version: 3.28.0-1
Severity: serious
Tags: sid trixie

cmake ftbfs on ppc64el (and ppc64):

[...]
99% tests passed, 5 tests failed out of 697

Label Time Summary:
CMake      = 1205.59 sec*proc (290 tests)
CUDA       =  90.91 sec*proc (11 tests)
HIP        =  17.89 sec*proc (6 tests)
ISPC       =  60.92 sec*proc (6 tests)
Label1     =   0.06 sec*proc (1 test)
Label2     =   0.06 sec*proc (1 test)
Qt5        = 678.18 sec*proc (49 tests)
command    =   6.93 sec*proc (23 tests)
policy     =  81.42 sec*proc (42 tests)
run        = 1198.66 sec*proc (267 tests)

Total Test time (real) = 436.62 sec

The following tests FAILED:
        108 - LibName (SEGFAULT)
        241 - CMakeCommands.add_link_options (SEGFAULT)
        264 - CTestTestDepends (Failed)
        393 - RunCMake.FPHSA (SEGFAULT)
        467 - RunCMake.cmake_path (SEGFAULT)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8
make[2]: Leaving directory '/<<PKGBUILDDIR>>/Build'

--- End Message ---
--- Begin Message ---
Version: 1.48.0-1

On Sat, Jan 13, 2024 at 03:49:17PM +0100, John Paul Adrian Glaubitz wrote:
> Control: tags -1 +patch
> 
> On Fri, 2024-01-12 at 01:31 +0100, John Paul Adrian Glaubitz wrote:
> > This has now been tracked down to the libuv upstream change that introduced 
> > support
> > for io_uring [1]. This regression is tracked now in a new issue for libuv 
> > [2].
> 
> The attached patch disables io_uring on ppc64 and ppc64el for the time being 
> until
> the upstream issue has been resolved.

This patch has been included in upstream 1.48.0, which fixed this issue.

Disabling misses out on the performance improvements by this change,
but it still works as good as before io_uring support was added.

> Adrian
>...

cu
Adrian

--- End Message ---

Reply via email to