Bug #25844 "make test" does not find mysql-test-run.pl
Submitted: 25 Jan 2007 11:08 Modified: 12 Feb 2007 14:00
Reporter: Ingo Strüwing Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Compiling Severity:S2 (Serious)
Version:5.0.36 OS:
Assigned to: Ingo Strüwing CPU Architecture:Any

[25 Jan 2007 11:08] Ingo Strüwing
After calling "make test-force", the normal mode tests (test-ns) work, and then:

xa                             [ pass ]             22
Stopping All Servers
Shutting-down Instance Manager
skipped 9 bytes from file: socket (3)
All 459 tests were successful.
The servers were restarted 114 times
Spent 1492.986 seconds actually executing testcases

/usr/bin/perl ./mysql-test-run.pl --force --ps-protocol
Can't open perl script "./mysql-test-run.pl": No such file or directory
make[1]: *** [test-ps] Error 2
make[1]: Leaving directory `/home2/mytest/mysql-5.0-team'
make: *** [test-force] Error 2

The Makefile has:

        /usr/bin/perl ./mysql-test-run.pl $(force) --ps-protocol

        cd mysql-test ; \
        /usr/bin/perl ./mysql-test-run.pl $(force)

test:   test-ns test-ps

In 5.1 "make test-force" works. In the 5.1 Makefile we have "cd mysql-test ; \" in every test target. So it may work for 5.0 too.

How to repeat:
Build a 5.0.36. Then run:
make test-force

Suggested fix:
Add one line to the Makefile:

+        cd mysql-test ; \
         /usr/bin/perl ./mysql-test-run.pl $(force) --ps-protocol

         cd mysql-test ; \
         /usr/bin/perl ./mysql-test-run.pl $(force)

 test:   test-ns test-ps
[1 Feb 2007 15:00] 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:


ChangeSet@1.2393, 2007-02-01 15:59:51+01:00, istruewing@chilla.local +1 -0
  Bug#25844: "make test" does not find mysql-test-run.pl
  Need to change directory before calling mysql-test-run.pl
[2 Feb 2007 7:50] Ingo Strüwing
Queued to 5.0-engines
[12 Feb 2007 14:00] Ingo Strüwing
Pushed to 5.0.36.
No changelog entry required. The bug appeared and was fixed between two releases.