Details
-
Task
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
Sometimes mysqld crashes leaving a dmp file, which can be used to output stack traces, local variables etc on buildbot
However mtr is not using it . It used to do so in the past, and would cdb debugger (which is installed on the machines) which would produce a lot of helpful for troubleshooting information
Recent example of mysql.dmp found and ignored.
From http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/2033/steps/test/logs/stdio
CURRENT_TEST: main.bootstrap
|
mysqltest: At line 45: command "$MYSQLD_BOOTSTRAP_CMD < $MYSQLTEST_VARDIR/tmp/long_query.sql >> $MYSQLTEST_VARDIR/tmp/bootstrap.log 2>&1" failed with wrong error: 255
|
|
|
The result from queries just before the failure was:
|
drop table if exists t1;
|
drop table t1;
|
drop table t1;
|
ERROR 42S02: Unknown table 'test.t1'
|
set @my_max_allowed_packet= @@max_allowed_packet;
|
set global max_allowed_packet=100*@@max_allowed_packet;
|
|
|
- saving 'D:/win32-debug/build/mysql-test/var/3/log/main.bootstrap/' to 'D:/win32-debug/build/mysql-test/var/log/main.bootstrap/'
|
- found 'mysqld.dmp' (0/5)
|
Server work done with
MDEV-29025There is no upload of logs or dmp file from the windows builder.
recent example: https://buildbot.mariadb.org/#/builders/234/builds/30651/steps/9/logs/stdio -> outputs to https://ci.mariadb.org/47982/logs/ - no amd64-windows