[Bug 1915275] Re: mysql-8.0 regressed on riscv64 due to new glibc

Fri Mar 12 06:48:36 UTC 2021

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 at ubuntu:~$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
  mysql-server-core-8.0-dbgsym
The following NEW packages will be installed:
  libmd0
The following packages will be upgraded:
  libbsd0 mysql-client-8.0 mysql-client-core-8.0 mysql-server mysql-server-8.0 mysql-server-core-8.0
6 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 20.8 MB/25.1 MB of archives.
After this operation, 277 MB disk space will be freed.
Do you want to continue? [Y/n] Y
Get:1 http://ppa.launchpad.net/ci-train-ppa-service/4487/ubuntu hirsute/main riscv64 mysql-server-8.0 riscv64 8.0.23-3ubuntu1~ppa1 [1185 kB]
Get:2 http://ppa.launchpad.net/ci-train-ppa-service/4487/ubuntu hirsute/main riscv64 mysql-server-core-8.0 riscv64 8.0.23-3ubuntu1~ppa1 [19.6 MB]
Fetched 20.8 MB in 6s (3499 kB/s)                
Preconfiguring packages ...
(Reading database ... 76902 files and directories currently installed.)
Preparing to unpack .../mysql-client-core-8.0_8.0.23-3ubuntu1~ppa1_riscv64.deb ...
Unpacking mysql-client-core-8.0 (8.0.23-3ubuntu1~ppa1) over (8.0.23-3build1) ...
Preparing to unpack .../mysql-client-8.0_8.0.23-3ubuntu1~ppa1_riscv64.deb ...
Unpacking mysql-client-8.0 (8.0.23-3ubuntu1~ppa1) over (8.0.23-3build1) ...
(Reading database ... 76902 files and directories currently installed.)
Removing mysql-server-core-8.0-dbgsym (8.0.23-3build1) ...
(Reading database ... 76827 files and directories currently installed.)
Preparing to unpack .../mysql-server-8.0_8.0.23-3ubuntu1~ppa1_riscv64.deb ...
Unpacking mysql-server-8.0 (8.0.23-3ubuntu1~ppa1) over (8.0.23-3build1) ...
Preparing to unpack .../mysql-server-core-8.0_8.0.23-3ubuntu1~ppa1_riscv64.deb ...
Unpacking mysql-server-core-8.0 (8.0.23-3ubuntu1~ppa1) over (8.0.23-3build1) ...
Preparing to unpack .../mysql-server_8.0.23-3ubuntu1~ppa1_all.deb ...
Unpacking mysql-server (8.0.23-3ubuntu1~ppa1) over (8.0.23-3build1) ...
Selecting previously unselected package libmd0:riscv64.
Preparing to unpack .../libmd0_1.0.3-3build1_riscv64.deb ...
Unpacking libmd0:riscv64 (1.0.3-3build1) ...
Preparing to unpack .../libbsd0_0.11.3-1build1_riscv64.deb ...
Unpacking libbsd0:riscv64 (0.11.3-1build1) over (0.10.0-1) ...
Setting up mysql-client-core-8.0 (8.0.23-3ubuntu1~ppa1) ...
Setting up mysql-server-core-8.0 (8.0.23-3ubuntu1~ppa1) ...
Setting up libmd0:riscv64 (1.0.3-3build1) ...
Setting up mysql-client-8.0 (8.0.23-3ubuntu1~ppa1) ...
Setting up libbsd0:riscv64 (0.11.3-1build1) ...
Setting up mysql-server-8.0 (8.0.23-3ubuntu1~ppa1) ...
Renaming removed key_buffer and myisam-recover options (if present)
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 2684
Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service → /lib/systemd/system/mysql.service.
Setting up mysql-server (8.0.23-3ubuntu1~ppa1) ...
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for libc-bin (2.33-0ubuntu2) ...

Starting the binary as before:

8.0.23-3ubuntu1~ppa1
ubuntu at ubuntu:~$ mysqld --verbose --help --innodb-read-only
mysqld  Ver 8.0.23-3ubuntu1~ppa1 for Linux on riscv64 ((Ubuntu))
Copyright (c) 2000, 2021, Oracle and/or its affiliates.
...

All good, now looking for an upload by racb now

** Changed in: mysql-8.0 (Ubuntu)
     Assignee: (unassigned) => Robie Basak (racb)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1915275

Title:
  mysql-8.0 regressed on riscv64 due to new glibc

Status in MySQL Server:
  Unknown
Status in glibc package in Ubuntu:
  Invalid
Status in mysql-8.0 package in Ubuntu:
  Triaged
Status in php7.4 package in Ubuntu:
  Invalid

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://launchpad.net/ubuntu/+source/mysql-8.0/8.0.23-1ubuntu1/+build/20983618

  I'm currently building on bileto with release pocket, to have a fast migration, because this is blocking some reverse-dependencies such as boinc from building correctly on riscv64.
  make[1]: Entering directory '/<<PKGBUILDDIR>>'
  RULES.override_dh_auto_test
  touch builddir/mysql-test/skiplist
  # Tests that are known to be unstable on all platforms are skipped
  # http://bugs.mysql.com/bug.php?id=83340
  echo "main.xa_prepared_binlog_off	: BUG#00000 - unstable test" >> builddir/mysql-test/skiplist
  echo "main.mysql_client_test		: BUG#100274 - unstable test" >> builddir/mysql-test/skiplist
  echo "main.type_float			: BUG#92375 - fails on ppc64el. Ref https://bugs.mysql.com/bug.php?id=92375" >> builddir/mysql-test/skiplist
  echo "main.type_newdecimal		: BUG#92375 - Same as above" >> builddir/mysql-test/skiplist
  echo "main.type_ranges			: BUG#92375 - Same as above" >> builddir/mysql-test/skiplist
  # https://bugs.mysql.com/bug.php?id=86608
  echo "main.mysqlpump_basic		: BUG#00000 - needs openssl with zlib" >> builddir/mysql-test/skiplist
  # Test is broken for 32bit. Fixed upstream, so remove in 8.0.12+
  echo "main.window_functions_explain	: BUG#00000 -  broken on i386" >> builddir/mysql-test/skiplist
  # Skip replication tests since they are timing sensitive and may
  # result in false positives.
  cd builddir/mysql-test && ./mtr --report-unstable-tests --parallel=8 --skip-rpl --suite=main --force --skip-test-list=./skiplist || true ;
  Logging: /<<PKGBUILDDIR>>/mysql-test/mysql-test-run.pl  --report-unstable-tests --parallel=8 --skip-rpl --suite=main --force --skip-test-list=./skiplist
  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>>/builddir/runtime_output_directory/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x62) [0x2aac5bb7d0]
  /<<PKGBUILDDIR>>/builddir/runtime_output_directory/mysqld(handle_fatal_signal+0x270) [0x2aab942e64]
  linux-vdso.so.1(__vdso_rt_sigreturn+0) [0x3ff7fe0800]
  /lib/riscv64-linux-gnu/libc.so.6(gsignal+0xa2) [0x3ff7420fec]
  /lib/riscv64-linux-gnu/libc.so.6(abort+0xb4) [0x3ff741198c]
  The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
  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-unstable-tests --force innodb_fts.mecab_utf8
  Logging: /<<PKGBUILDDIR>>/mysql-test/mysql-test-run.pl  --report-unstable-tests --force innodb_fts.mecab_utf8
  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>>/builddir/runtime_output_directory/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x62) [0x2aac5bb7d0]
  /<<PKGBUILDDIR>>/builddir/runtime_output_directory/mysqld(handle_fatal_signal+0x270) [0x2aab942e64]
  linux-vdso.so.1(__vdso_rt_sigreturn+0) [0x3ff7fe0800]
  /lib/riscv64-linux-gnu/libc.so.6(gsignal+0xa2) [0x3ff7420fec]
  /lib/riscv64-linux-gnu/libc.so.6(abort+0xb4) [0x3ff741198c]
  The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
  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_dh_auto_test] Error 1
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/mysql-server/+bug/1915275/+subscriptions