This bug was fixed in the package glibc - 2.27-3ubuntu1.3
---
glibc (2.27-3ubuntu1.3) bionic; urgency=medium
[ Balint Reczey ]
* debian/gbp.conf: Add initial configuration
* debian/control.in/main: Add Vcs-* pointing to Ubuntu packaging repository
* arm64: Enable searching
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/ppc64el/g/glibc/20200911_170104_5f83a@/log.gz
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
Hello Thadeu, or anyone else affected,
Accepted glibc into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.27-3ubuntu1.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Launchpad has imported 6 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=24744.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
This test was removed by upstream in recent versions.
** Changed in: glibc (Ubuntu)
Status: Invalid => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853193
Title:
** Tags added: testcase
** Changed in: glibc (Ubuntu)
Importance: Undecided => Medium
** Changed in: glibc (Ubuntu Bionic)
Importance: Undecided => Medium
** Bug watch added: Sourceware.org Bugzilla #24744
https://sourceware.org/bugzilla/show_bug.cgi?id=24744
** Also affects: glibc
** Patch added: "fix for bionic"
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/+attachment/5388335/+files/glibc_2.27-3ubuntu1.1.debdiff
** Description changed:
+ [Impact]
+ When tested against newer versions of linux, glibc tests will fail as it
makes some assumptions about
I am sending a proposed patch. I am building a package that includes
that patch on my ppa:cascardo/ppa. I will trigger tests against that and
verify this really fixes the issue.
** Patch added: "disable cross_device_failure test for copy_file_range"
