Bug #36029 Test funcs_1.<engine>_trig_0407 failing on Windows
Submitted: 13 Apr 2008 15:27 Modified: 6 May 2008 18:36
Reporter: Patrick Crews Email Updates:
Status: Closed Impact on me:
None 
Category:Tests: Server Severity:S3 (Non-critical)
Version:5.1 OS:Microsoft Windows
Assigned to: Patrick Crews CPU Architecture:Any
Tags: funcs_1, mysql-test-run, Tests, windows
Triage: D3 (Medium)

[13 Apr 2008 15:27] Patrick Crews
Description:
Test funcs_1.<engine>_trig_0407 failing on Windows systems

This appears to be a failure of mysql-test-run's --replace_result option.

The tests use this to try to mitigate results that vary on each run:
12887: -connect(localhost,test_noprivs,PWD,test,MASTER_MYPORT,MASTER_MYSOCK);
12888: -connect(localhost,test_yesprivs,PWD,test,MASTER_MYPORT,MASTER_MYSOCK);
12889:
+connect(localhost,test_noprivs,PWD,test,MASTER_MYPORT,\tmp\fiAKHARxar\master.sock);
12890:
+connect(localhost,test_yesprivs,PWD,test,MASTER_MYPORT,\tmp\fiAKHARxar\master.sock);

For some reason, the value of $MASTER_MYSOCK isn't being replaced.  (verified that this
occurs with other variables as well:  $MYISAMPACK, $MYISAMCHK, etc -- will write a
separate bug for this and refer to it here)

How to repeat:
Run innodb_trig_0407.test on a Windows system using MySQL 5.1

From the mysql-test directory, execute the following command:

./mysql-test-run.pl --suite=funcs_1 innodb_trig_03e

You will see failures as shown in the example above.  These appear to be the only
differences between expected and actual results.

Suggested fix:
1)  Temp-fix - disable the failing sub-tests within this test so that some test
functionality remains
2)  Fix mysql-test-run so that --replace_result will work for these path-containing
variables
3)  Re-enable the original test once mysql-test-run is behaving properly.
[6 May 2008 0:25] Bugs System
Pushed into 5.0.62
[6 May 2008 0:29] Bugs System
Pushed into 5.1.25-rc
[6 May 2008 0:33] Bugs System
Pushed into 6.0.6-alpha
[6 May 2008 18:36] Paul Dubois
Test suite changes. No changelog entry needed.