Bug #28333 Test "flush" tries to create a new thread - on only one platform
Submitted: 9 May 2007 13:56 Modified: 14 Jun 2007 19:45
Reporter: Joerg Bruehe Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Embedded Library ( libmysqld ) Severity:S1 (Critical)
Version:5.1.19-beta OS:Linux (Debian PPC)
Assigned to: Alexey Botchkov CPU Architecture:Any

[9 May 2007 13:56] Joerg Bruehe
Description:
Test "flush" works everywhere, including embedded,
*except* for Debian-PPC-embedded:

=====
flush                          [ fail ]

Errors are (from /PATH/mysqltest-time) :
mysqltest: At line 26: Cannot start new thread for query
(the last lines may be the most important ones)
Result from queries before failure can be found in /PATH/mysql-test/var/log/flush.log
=====

Line 26 is the closing brace '}' of the while loop in the test file.

How to repeat:
Run embedded tests on that host.
[8 Jun 2007 20:39] 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/28435

ChangeSet@1.2514, 2007-06-09 00:39:23+05:00, holyfoot@mysql.com +1 -0
  Bug #28333 Test "flush" tries to create a new thread - on only one platform
  
  on PPC/Debian Linux default stack size for a thread is too big.
  As we use default thread settings in mysqltest, the
  thread creation fails if we create lots of threads (as it
  happens in flush.test). So now stack size is explicitly specified
  for the mysqltest
[9 Jun 2007 9:38] Alexander Barkov
The patch is ok to push.
[14 Jun 2007 18:59] Bugs System
Pushed into 5.1.20-beta
[14 Jun 2007 19:00] Bugs System
Pushed into 5.0.44
[14 Jun 2007 19:45] Paul Dubois
Noted in 5.0.44, 5.1.20 changelogs.

mysqltest used a too-large stack size on PPC/Debian Linux, causing
thread-creation failure for tests that use many threads.