glibc in eoan building against the supposedly-fixed kernel is hitting
these issues again on i386 testsuites. Did we break it again?
https://launchpad.net/ubuntu/+source/glibc/2.29-0ubuntu3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package linux - 4.4.0-150.176
---
linux (4.4.0-150.176) xenial; urgency=medium
* linux: 4.4.0-150.176 -proposed tracker (LP: #1830941)
* glibc 2.23-0ubuntu11 ADT test failure with linux 4.4.0-149.175
(LP: #1830890)
- x86/vdso: Pass
ADT glibc testcases are now successful:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/g/glibc/20190530_100415_f7174@/log.gz
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830890
Title:
glibc 2.23-0ubuntu11 ADT test failure with linux
** Description changed:
- Testing failed on:
- i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/g/glibc/20190528_085308_d03ca@/log.gz
+ [Impact]
+ Some glibc testcases are regressing on i386 after the following
Confirmed to be caused by:
commit 379d98ddf41344273d9718556f761420f4dc80b3
Author: Alistair Strachan
Date: Fri Aug 3 10:39:31 2018 -0700
x86: vdso: Use $LD instead of $CC to link
And fixed by:
commit cd01544a268ad8ee5b1dfe42c4393f1095f86879
Author: Alistair Strachan
Date: Fri Dec 14
This might me related to the issue reported on bug 1805154, which would
be a a regression in the vdso caused by
379d98ddf41344273d9718556f761420f4dc80b3 "x86: vdso: Use $LD instead of
$CC to link". This commit has been applied to xenial as part of upstream
stable update 4.4.179.
--
You received
Failed testcases:
FAIL: debug/tst-backtrace5
FAIL: nptl/tst-cancel24
FAIL: nptl/tst-cancelx16
FAIL: nptl/tst-cancelx18
FAIL: nptl/tst-cancelx20
FAIL: nptl/tst-cancelx21
FAIL: nptl/tst-cancelx4
FAIL: nptl/tst-cancelx5
FAIL: nptl/tst-cond25
FAIL: nptl/tst-cond8
FAIL: nptl/tst-cond8-static
FAIL:
