Details
Description
As of now, happened 3 times according to the cross-reference report:
http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-quantal-x86/builds/1484
http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-quantal-x86/builds/1479
http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-quantal-x86/builds/1299
main.mysqld--help 'unix' w2 [ fail ] timeout after 900 seconds
Test ended at 2014-12-06 13:16:11
Test case timeout after 900 seconds
== /run/shm/var_auto_hGGZ/2/log/mysqld--help.log ==
== /run/shm/var_auto_hGGZ/2/tmp/analyze-timeout-mysqld.1.err ==
mysqltest: Could not open connection 'default': 2013 Lost connection to MySQL server at 'reading initial communication packet', system error: 104 "Connection reset by peer"
- saving '/run/shm/var_auto_hGGZ/2/log/main.mysqld--help-unix/' to '/usr/local/mariadb-10.1.2-linux-i686/mysql-test/var/log/main.mysqld--help-unix/'
Retrying test main.mysqld--help, attempt(2/3)...
worker[2] > Restart - not started
***Warnings generated in error logs during shutdown after running tests: main.mysql_cp932 main.mysql_comments main.mysql_not_windows main.mysql-bug41486 main.mysqld--defaults-file main.mysql_upgrade_no_innodb main.mysql_locale_posix main.mysql5613mysql main.mysql_tzinfo_to_sql_symlink main.mysql_protocols main.mysqld--help main.mysqladmin main.mysql-bug45236
Attempting backtrace. You can use the following information to find out
main.mysqld--help 'unix' w2 [ retry-pass ] 68
Always on 10.1*, always on kvm-bintar-quantal-x86.
Different slaves.
Couldn't reproduce it so far on the same VM image with the same sequence of tests
Gliffy Diagrams
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Last time it happened was 2015-01-10, and on 2015-01-11 there was this commit
commit 2501a0ea59509ff5b8644adbe229ae16a8a11718 3fcbd7cb47b1b251d3d541c9e67c1a0b7d53fdc0 Author: Sergei Golubchik <serg@mariadb.org> Date: Sun Jan 11 16:37:25 2015 +0100 MDEV-7364 - mysqld --help --verbose prints random values for "debug" better fix that doesn't make debug-dbug variable to disappear from mysqld --help output (this fact is used by have_debug.inc) and shows correctly what dbug value was set on the command line.Hopefully it fixed the problem. Closing for now, Will re-open if it happens again.