This bug was fixed in the package mysql-8.0 - 8.0.23-3ubuntu1
---
mysql-8.0 (8.0.23-3ubuntu1) hirsute; urgency=medium
[ Frans Spiesschaert ]
* Update nl.po translation file (Closes: #970039)
[ Helge Kreutzmann ]
* Update de.po translation file (Closes: #968847)
[
** Changed in: mysql-8.0 (Ubuntu)
Status: Triaged => 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/1915275
Title:
mysql-8.0 regressed on riscv64 due to new glibc
To manage
FYI Builds completed just fine for all arches in https://launchpad.net
/~ci-train-ppa-service/+archive/ubuntu/4487/+packages
Furthermore using that PPA it really works to install now
ubuntu@ubuntu:~$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading
Excellent work tracking this down Christian; I appreciated being able to
follow along with your detailed analysis.
Marking this not a php7.4 bug specifically, but will make sure php7.4
rebuilds once this is in.
** Changed in: php7.4 (Ubuntu)
Status: New => Invalid
--
You received this
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915275
Title:
mysql-8.0 regressed on riscv64 due to new glibc
To manage notifications
Submitted to Debian (for an upload there into experimental and into Hirsute)
=> https://salsa.debian.org/mariadb-team/mysql/-/merge_requests/46
Test PPA:
=> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4487/+packages
--
You received this bug notification because you are a member
Submitted upstream as https://bugs.mysql.com/bug.php?id=102926
** Bug watch added: MySQL Bug System #102926
http://bugs.mysql.com/bug.php?id=102926
** Also affects: mysql-server via
http://bugs.mysql.com/bug.php?id=102926
Importance: Unknown
Status: Unknown
--
You received this
And that awkward number if directly consumed is just "-1"
$ cat test-sysconf.cpp
#include
#include
int main() {
std::cout << "_SC_LEVEL1_DCACHE_LINESIZE = " <<
sysconf(_SC_LEVEL1_DCACHE_LINESIZE) << "\n";
return 0;
}
$ rm test-sysconf; g++ -Wall -o test-sysconf test-sysconf.cpp &&
I have separated the problem from all the mysql code.
This file here works on x86 and on older riscv64.
But if ran on current hirsute riscv64 it breaks as mysql-server-8.0 does.
I further simplified it and attach it hereby for debugging.
It seems that the detection of the cache-line-size is
Ok I found in the stdc++ implementation of "new" that sz indeed is passed to
malloc.
void *ptr = std::malloc(sz))
Thereby it indeed means "bytes" and that means ~18 exabyte which is slightly
more than most systems can offer :-)
The question now becomes, where is this value created/derived
In my comparison on Focal (older libc / stdc++) all calls to "operator new[]"
and "operator new" had sz=0 like:
Breakpoint 5, operator new (sz=0) at
../../../../src/libstdc++-v3/libsupc++/new_op.cc:47
The first operator new that didn't have sz=0 in this good case was a totally
different
>From the backtrace at frist we see:
At the start of mysql it calls init_server_components -> delegates_init.
That then initializes a new object
alignas(Trans_delegate) static char place_trans_mem[sizeof(Trans_delegate)];
...
transaction_delegate = new (place_trans_mem) Trans_delegate;
I was following:
- https://dev.mysql.com/doc/refman/8.0/en/using-gdb-on-mysqld.html I
- https://dev.mysql.com/doc/refman/8.0/en/crashing.html
Which mostly comes down to:
$ apt source mysql-server-8.0
$ apt install gdb mysql-server-core-8.0-dbgsym libc6-dbg libstdc++6-dbgsym
$ sudo gdb
Note for everyone that wants to retry, follow https://wiki.ubuntu.com/RISC-V
which works fine in e.g. a hirsute LXD container without messing anything up in
your main system.
After eliminating all of the postinst and config this can be triggered by the
test-for-startability call like:
$
I was able to reproduce this in a riscv64 qemu emulation.
IMHO one central issue in handling the bug so far was the assumption that this
"only" breaks the tests. It does not, it makes mysql-server totally
unusable/uninstallable.
And by uninstallable it also FTBFSes all that is listed by
$
That's now making php7.4 fails to build on riscv64 which is needed to
complete the libzip transition
** Changed in: mysql-8.0 (Ubuntu)
Importance: Undecided => High
** Tags added: rls-hh-incoming
** Also affects: php7.4 (Ubuntu)
Importance: Undecided
Status: New
** Changed in:
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915275
Title:
mysql-8.0 regressed on riscv64 due to new glibc
To manage notifications about this bug go to:
It is a real regression, but needs triaging and should not hold back
glibc's landing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915275
Title:
mysql-8.0 regressed on riscv64 due to new glibc
I'm going to disable the tests for mysql-8.0 on riscv64, but this is a
real regression and now riscv64 will have a broken mysql-8.0 then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915275
Title:
The only difference between bileto and the archive build is that bileto
has been run against only release pocket, nothing else.
So tests seems to be run on both release/proposed/bileto.
Ok about disabling the test run, but in any case the bug looks real and
breaking the whole mysql on riscv64.
src:mysql-8.0 is supposed to honour nocheck already, I think, via
debhelper (it only overrides dh_auto_test). Did you get the test run
because the riscv64 nocheck disablement doesn't apply to bileto?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
> ...because the riscv64 nocheck disablement doesn't apply to bileto?
To be clear, I'm not asserting that; I'm asking.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915275
Title:
mysql-8.0
i wonder if that also fails on more recent riscv64 kernels, i.e. on 5.8.
however our builders are still on v5.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915275
Title:
mysql-8.0 regressed on
Build-time tests are disabled on riscv64 by default: LP: #1891686.
This may be a real regression, but in itself this should not be enough to hold
back glibc from migrating.
Please disable the test on riscv64 if needed in mysql-8.0 and we can
triage this separately.
** Changed in: glibc (Ubuntu)
24 matches
Mail list logo
