Bug #41889 Test main.innodb_bug38231 is failing w/embedded server (server crash)

• Submitted: 5 Jan 2009 22:49
• Modified: 21 Jan 2009 16:23
• Reporter: Patrick Crews
• Status: Closed
• Category: Tests: Server
• Severity: S3 (Non-critical)
• Version: 5.1+
• OS: Any
• Assigned to: Davi Arnaut
• CPU Architecture: Any
• Tags: embedded server, pushbuild

[5 Jan 2009 22:49] Patrick Crews

Description:
Test main.innodb_bug38231 is failing on Pushbuild w/ the embedded server option.

The failure is a likely server crash:
main.innodb_bug38231           [ fail ]

ERROR: mysqltest returned unexpected code 134, it has probably crashed

How to repeat:
Run the test with the embedded server:

From the mysql-test directory, execute the following:
./mysql-test-run --force --embedded server innodb_bug38231

Observer mysql-test-run's output

Suggested fix:
Determine if this is an expected change in the server w/o an update to the test or an actual server bug.

If it is the former, correct the test's expectations to reflect proper server behavior, otherwise, reassign the bug to a developer for further research / correction.

[8 Jan 2009 12:32] 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/62681

2729 Davi Arnaut	2009-01-08
      Bug#41889: Test main.innodb_bug38231 is failing w/embedded server (server crash)
      
      The problem is that a mysql connection instance is not thread-safe
      and reentrant, meaning that it can't be used concurrently and can't
      be re-entered while it's already running. This applies for any form
      of the server (embedded or not), but this rule can be violated in a
      test case if the test sends a new command without waiting for the
      result of previous command that was sent asynchronously and this can
      lead to hangs when over a network or to crashes under embedded server
      as the server query execution path will be re-entered concurrently
      with the same connection structure.
      
      The solution is to rework the test case so that the aforementioned
      rule is obeyed.

[8 Jan 2009 21:52] Timothy Smith

Patch looks fine.  It would be nice to have this checked in mysqltest.c (die with an error if --send is active and another query is attempted).

[13 Jan 2009 15:08] Davi Arnaut

Queued to 5.1-bugteam

[15 Jan 2009 6:40] Bugs System

Pushed into 5.1.31 (revid:[e-mail]-20090115053147-tx1oapthnzgvs1ro) (version source revid:[e-mail]-20090108123134-x204djl2e83ra391) (merge vers: 5.1.31) (pib:6)

[16 Jan 2009 3:50] Paul DuBois

Test case changes. No changelog entry needed.

Setting report to NDI pending push into 6.0.x.

[19 Jan 2009 11:24] Bugs System

Pushed into 5.1.31-ndb-6.2.17 (revid:[e-mail]-20090119095303-uwwvxiibtr38djii) (version source revid:[e-mail]-20090115073240-1wanl85vlvw2she1) (merge vers: 5.1.31-ndb-6.2.17) (pib:6)

[19 Jan 2009 13:01] Bugs System

Pushed into 5.1.31-ndb-6.3.21 (revid:[e-mail]-20090119104956-guxz190n2kh31fxl) (version source revid:[e-mail]-20090119104956-guxz190n2kh31fxl) (merge vers: 5.1.31-ndb-6.3.21) (pib:6)

[19 Jan 2009 15:57] Jon Stephens

Setting status back to NDI pending merge to 6.0 tree.

[19 Jan 2009 16:07] Bugs System

Pushed into 5.1.31-ndb-6.4.1 (revid:[e-mail]-20090119144033-4aylstx5czzz88i5) (version source revid:[e-mail]-20090119144033-4aylstx5czzz88i5) (merge vers: 5.1.31-ndb-6.4.1) (pib:6)

[20 Jan 2009 18:54] Bugs System

Pushed into 6.0.10-alpha (revid:[e-mail]-20090119171328-2hemf2ndc1dxl0et) (version source revid:[e-mail]-20090114143745-x2dvnmix6gjlt6z6) (merge vers: 6.0.10-alpha) (pib:6)

[21 Jan 2009 16:23] Paul DuBois

Test case changes. No changelog entry needed.