Hi!
Yes, I tried the build on the porterbox and it is crashing, and
repeated runs seem to crash on the same tests, but not exactly every
time.
Completed: Failed 14/1131 tests, 98.76% were successful.
Failing test(s): main.bind_address_resolution
main.bind_multiple_addresses_resolution
main.log_slow_always_query_time main.connect main.set_statement
main.unsafe_binlog_innodb
Completed: Failed 10/1130 tests, 99.12% were successful.
Failing test(s): main.bind_multiple_addresses_resolution
main.bind_address_resolution main.partition_innodb_semi_consistent
main.subselect_no_mat main.sp-i_s_columns
-----
Notes to self on how to build on stadler.debian.net:
ssh ssh stadler.debian.net
source porterbox.sh
pend # remove any old schroots
psetup # create a new schroot
pinstall git-buildpackage gdb debian-goodies libipc-system-simple-perl
# install prerequisites
pchroot # enter schroot
gbp clone --verbose vcs-git:mariadb # gbp not on host, must run from
inside schroot
exit
pdeps mariadb # install build dependencies
pchroot # enter again to start actual build
cd mariadb
gbp buildpackage --git-verbose --git-no-pristine-tar -us -uc
# rerun test after build when artifacts are still around using
# commands copied from buildlog
cd builddir/mysql-test
./mtr --force --testcase-timeout=120 --suite-timeout=540 --retry=3 \
--verbose-restart --max-save-core=1 --max-save-datadir=1 \
--parallel=48 --skip-rpl --suite=main \
--skip-test-list=/tmp/tmp.MTnxYcCghC
