| Bug #48918 | MTR uses an un-initialized value in comparison | ||
|---|---|---|---|
| Submitted: | 19 Nov 2009 18:26 | Modified: | 17 Jun 2010 19:38 |
| Reporter: | Joerg Bruehe | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Tools: MTR / mysql-test-run | Severity: | S3 (Non-critical) |
| Version: | 5.5.0-beta | OS: | Linux (SLES 9 RPM) |
| Assigned to: | Bjørn Munch | CPU Architecture: | Any |
[20 Nov 2009 13:01]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/91081 2861 Bjorn Munch 2009-11-20 Bug #48918 MTR uses an un-initialized value in comparison mysqld->{proc} not defined for an embedded server Check only if {proc} defined
[26 Nov 2009 10:34]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/91768 2865 Bjorn Munch 2009-11-26 Bug #48918 MTR uses an un-initialized value in comparison mysqld->{proc} not defined for an embedded server Check only if {proc} defined
[26 Nov 2009 11:45]
Bjørn Munch
Pushed to 5.1-mtr, trunk-mtr, next-mr-mtr, 6.0-codebase-mtr
[20 Feb 2010 9:31]
Bugs System
Pushed into 6.0.14-alpha (revid:alik@sun.com-20100220092844-jh07ayojyxn8uh9p) (version source revid:bjorn.munch@sun.com-20091126113643-14x9x1b5jw483wiv) (merge vers: 6.0.14-alpha) (pib:16)
[20 Feb 2010 9:33]
Bugs System
Pushed into 5.5.3-m2 (revid:alik@sun.com-20100220092622-wvhh1vfy5tjq4mhu) (version source revid:bjorn.munch@sun.com-20091126103637-xcfhi92t575tgo3q) (merge vers: 5.5.0-beta) (pib:16)
[20 Feb 2010 9:36]
Bugs System
Pushed into mysql-next-mr (revid:alik@sun.com-20100220092730-paoo5t9gcajs5dq8) (version source revid:bjorn.munch@sun.com-20091126110818-tmrskn0sw591eu9k) (pib:16)
[23 Feb 2010 2:11]
Paul DuBois
Changes to test suite. No changelog entry needed. Setting report to Need Merge pending push to 5.1.x, Celosia.
[1 Mar 2010 8:45]
Bugs System
Pushed into 5.1.45 (revid:joro@sun.com-20100301083827-xnimmrjg6bh33o1o) (version source revid:azundris@mysql.com-20100222175719-viuh0f3gdsrkgv0r) (merge vers: 5.1.45) (pib:16)
[1 Mar 2010 16:29]
Paul DuBois
No changelog entry needed.
[17 Jun 2010 11:57]
Bugs System
Pushed into 5.1.47-ndb-7.0.16 (revid:martin.skold@mysql.com-20100617114014-bva0dy24yyd67697) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)
[17 Jun 2010 12:36]
Bugs System
Pushed into 5.1.47-ndb-6.2.19 (revid:martin.skold@mysql.com-20100617115448-idrbic6gbki37h1c) (version source revid:martin.skold@mysql.com-20100609140708-52rvuyq4q500sxkq) (merge vers: 5.1.45-ndb-6.2.19) (pib:16)
[17 Jun 2010 13:23]
Bugs System
Pushed into 5.1.47-ndb-6.3.35 (revid:martin.skold@mysql.com-20100617114611-61aqbb52j752y116) (version source revid:vasil.dimov@oracle.com-20100331130613-8ja7n0vh36a80457) (merge vers: 5.1.46) (pib:16)
Description: This happened in the build of 5.5.0-beta, I cannot remember having seen it before (and the BugDB doesn't have a matching entry). I have it specific on one machine only, used to cerate RPMs for SLES 9, but that may be caused by some pure chance. I have it in "embedded" tests only, this might be more significant. The problem happens in 10 tests, until MTR aborts the suite. This one might be the most obvious one to show it is a problem in MTR: ===== timer 29464: expired after 900 seconds Use of uninitialized value in string eq at ./mysql-test-run.pl line 3938. worker[1] Trying to dump core for [mysqltest - pid: 29465, winpid: 29465] innodb.innodb-use-sys-malloc [ fail ] timeout after 900 seconds Test ended at 2009-11-18 01:11:08 Test case timeout after 900 seconds == /usr/src/packages/BUILD/mysql-5.5.0-beta/mysql-test/var/log/innodb-use-sys-malloc.log == - saving '/usr/src/packages/BUILD/mysql-5.5.0-beta/mysql-test/var/log/innodb.innodb-use-sys-malloc/' to '/usr/src/packages/BUILD/mysql-5.5.0-beta/mysql-test/var/log/innodb.innodb-use-sys-malloc/' Retrying test, attempt(2/3)... innodb.innodb-use-sys-malloc [ retry-pass ] 135 Retrying test, attempt(3/3)... innodb.innodb-use-sys-malloc [ retry-pass ] 129 ===== Looking at the test, I fail to see how it can hit a timeout: Neither does it involve any locks (which might run into deadlock) nor does it use large amounts of data or show any other reason for long run time. My guess is that the handling or behavior of "embedded" tests differs from the typical case of separate client and server sufficiently to cause wrong (re)actions. The list of all affected tests: main.lock_tables_lost_commit main.innodb_autoinc_lock_mode_zero main.innodb_bug39438 main.innodb_mysql main.innodb_lock_wait_timeout innodb.innodb-use-sys-malloc_1 main.myisam main.lowercase_mixed_tmpdir_innodb innodb.innodb-analyze innodb.innodb_bug36169 How to repeat: I can't tell for sure - for me, it was a normal release build. Maybe it will happen again on another "embedded" run of SLES 9 RPM build, maybe some other parallel activity was important to cause this.