MySQL Bugs: #36788: Multiple funcs_1 'trig' tests are failing on vanilla builds

Bug #36788	Multiple funcs_1 'trig' tests are failing on vanilla builds
Submitted:	18 May 2008 21:38	Modified:	29 Jul 2008 9:54
Reporter:	Patrick Crews	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Tests: Server	Severity:	S3 (Non-critical)
Version:	5.0+	OS:	Any
Assigned to:	Matthias Leich	CPU Architecture:	Any
Tags:	charset, funcs_1, Tests
Triage:	D3 (Medium)

Description:
Multiple funcs_1 'trig' tests are failing on vanilla server builds:
Enterprise, Classic , Pushbuild or Source-without-max build (suspect all of these are affected).
only the myisam and ndb variants seem to be affected as these are the only engines in the more basic builds.
The following tests are affected:
<engine>_trig_102
<engine>_trig_03
<engine>_trig_0407
<engine>_trig_08
<engine>_trig_09
<engine>_trig_1011ext

All of these use the include file: suite/funcs_1/include/<engine>_tb3.inc
This include file is trying to use the ucs2 character set, which is no longer included in these builds.

This failure is related to Bug #36787	Test funcs_1.charset_collation_1 failing

How to repeat:
Build a version of 5.1+ with BUILD/compile-dist

Run the tests:
./mysql-test-run --suite=funcs_1 --do-test trig.

Observe the failures:  (output snipped for brevity)

mysqltest: In included file "./suite/funcs_1/include/ndb_tb3.inc": At line 6: query 'create table tb3 (
...
failed: 1115: Unknown character set: 'ucs2'

Suggested fix:
This is tied to Bug #36787	Test funcs_1.charset_collation_1 failing
As such, we need to determine if ucs2 is or is not supposed to be a part of these particular builds

If it is no longer included with the builds, the test needs to be altered so that this character set is no longer used.

If the character set *is* supposed to be a part of the build, then the resolution of Bug#36787 will also correct this bug (ucs2 will be available again).

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/47262

Ok to push.

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/47340

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/47347

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/47359

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/47360

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/47361

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/47362

Patch pushed to
mysql-5.0-bugteam
mysql-5.1-bugteam
mysql-6.0-bugteam

Pushed into 5.0.68, 5.1.28 and 6.0.7-alpha

Pushed into 5.0.64  (revid:mleich@mysql.com-20080602195711-ltzn2r0y2dkmo93m) (pib:2)
(Retry automatic marking, to ensure nothing is missed. cm01)

Pushed into 5.1.27  (revid:joerg@mysql.com-20080626161101-h5hsaluwtf05xdr2) (version source revid:joerg@mysql.com-20080626161101-h5hsaluwtf05xdr2) (pib:3)

Test case change. No 5.0.x/5.1.x changelog entry needed.

Setting report to Patch Queued pending push of fix into 6.0.x.

Pushed to 6.0.7-alpha

Closed per comment from Paul.