Dear HPPA porters,

We would like to push glibc 2.24 currently in experimental into sid in
the next weeks. It is going to be the version we ship in Stretch.

I have looked at the testsuite results from the latest uploads, there
are 9 real regressions (ie not new tests) mostly related to NPTL:

* FAIL: nptl/tst-default-attr
    original exit status 22
    stacksize test
    guardsize test
    sched test
    tst-default-attr.c:101: pthread_create returned 22 (errno = 22)
    tst-default-attr.c:371: do_sched_test returned 22 (errno = 22)

The test hasn't changed recently.


* FAIL: rt/tst-timer4
    original exit status 1
    clock_gettime returned timespec = { 1469505650, 981046459 }
    clock_getres returned timespec = { 0, 4000000 }
    Timed out: killed the child process

* FAIL: rt/tst-timer5
    original exit status 1
    clock_gettime returned timespec = { 1665713, 650390357 }
    clock_getres returned timespec = { 0, 4000000 }
    Timed out: killed the child process

The above two seems related.


* FAIL: nptl/tst-cancel-self
    original exit status 1
    Didn't expect signal from child: got `Segmentation fault'

* FAIL: nptl/tst-cancel-self-cancelstate
    original exit status 1
    Didn't expect signal from child: got `Segmentation fault'

* FAIL: nptl/tst-cancel12
    original exit status 1
    Didn't expect signal from child: got `Segmentation fault'

* FAIL: nptl/tst-cancel14
    original exit status 1
    Didn't expect signal from child: got `Segmentation fault'

* FAIL: nptl/tst-cancelx12
    original exit status 1
    Didn't expect signal from child: got `Segmentation fault'

* FAIL: nptl/tst-cancelx14
    original exit status 1
    Didn't expect signal from child: got `Segmentation fault'

The above 6 failures appeared when switching from GCC 5 to GCC 6 and
looks like quite worrisome.


Given that GCC 5 is going to be removed soon, we have to build the GNU
libc with GCC 6. Could you please have a look at the issues?

Thanks,
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurel...@aurel32.net                 http://www.aurel32.net


Reply via email to