mysql-8.0 regressed on riscv64 due to new glibc
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL Server |
Unknown
|
Unknown
|
|||
glibc (Ubuntu) |
Invalid
|
Low
|
Unassigned | ||
mysql-8.0 (Ubuntu) |
Fix Released
|
Critical
|
Robie Basak | ||
php7.4 (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
Hello, looks like mysql-8.0 can't run anymore its testsuite on riscv64, due to a probable bug in glibc.
See e.g.
https:/
I'm currently building on bileto with release pocket, to have a fast migration, because this is blocking some reverse-
make[1]: Entering directory '/<<PKGBUILDDIR>>'
RULES.override_
touch builddir/
# Tests that are known to be unstable on all platforms are skipped
# http://
echo "main.xa_
echo "main.mysql_
echo "main.type_float : BUG#92375 - fails on ppc64el. Ref https:/
echo "main.type_
echo "main.type_ranges : BUG#92375 - Same as above" >> builddir/
# https:/
echo "main.mysqlpump
# Test is broken for 32bit. Fixed upstream, so remove in 8.0.12+
echo "main.window_
# Skip replication tests since they are timing sensitive and may
# result in false positives.
cd builddir/mysql-test && ./mtr --report-
Logging: /<<PKGBUILDDIR>
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
18:50:20 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x46000
/<<PKGBUILDDIR>
/<<PKGBUILDDIR>
linux-vdso.
/lib/riscv64-
/lib/riscv64-
The manual page at http://
information that should help you find out what is causing the crash.
mysql-test-run: *** ERROR: Could not find version of MySQL
cd builddir/mysql-test && ./mtr --report-
Logging: /<<PKGBUILDDIR>
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
18:50:24 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x46000
/<<PKGBUILDDIR>
/<<PKGBUILDDIR>
linux-vdso.
/lib/riscv64-
/lib/riscv64-
The manual page at http://
information that should help you find out what is causing the crash.
mysql-test-run: *** ERROR: Could not find version of MySQL
make[1]: *** [debian/rules:154: override_
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:226: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2
tags: | added: server-next |
Changed in glibc (Ubuntu): | |
status: | New → Invalid |
Changed in mysql-8.0 (Ubuntu): | |
status: | Triaged → Fix Committed |
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.