Bug #96048 innodb_stress fails because it uses wrong path for load_generator.py on CentOS 7
Submitted: 1 Jul 2019 14:03 Modified: 2 Jul 2019 12:49
Reporter: Hrvoje Matijakovic Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Tests Severity:S7 (Test Cases)
Version:5.7.26 OS:CentOS
Assigned to: CPU Architecture:x86

[1 Jul 2019 14:03] Hrvoje Matijakovic
Description:
Running the innodb.stress fails because it uses wrong path for load_generator.py on CentOS 7:

[root@centos7 mysql-test]# ./mtr innodb_stress.innodb_stress
Logging: ./mtr  innodb_stress.innodb_stress
MySQL Version 5.7.26
Checking supported features...
 - SSL connections supported
Collecting tests...
Removing old var directory...
Creating var directory '/usr/share/mysql-test/var'...
Installing system database...
Using parallel: 1

==============================================================================

TEST                                      RESULT   TIME (ms) or COMMENT
--------------------------------------------------------------------------

worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 13000..13009
worker[1] mysql-test-run: WARNING: running this script as _root_ will cause some tests to be skipped
[100%] innodb_stress.innodb_stress              [ fail ]
        Test ended at 2019-07-01 13:54:48

CURRENT_TEST: innodb_stress.innodb_stress
python: can't open file '/usr//mysql-test/suite/innodb_stress/t/load_generator.py': [Errno 2] No such file or directory
mysqltest: In included file ./suite/innodb_stress/include/innodb_stress.inc at line 83:
included from /usr/share/mysql-test/suite/innodb_stress/t/innodb_stress.test at line 37:
At line 83: command "$exec" failed

Output from before failure:
exec of 'python /usr//mysql-test/suite/innodb_stress/t/load_generator.py /usr/share/mysql-test/var/run/mysqld.1.pid 0 1000  2 10 root 127.0.0.1 13000 test 0 4096 /usr/share/mysql-test/var/tmp/load_generator 0 0 0' failed, error: 512, stat
us: 2, errno: 2

File can be found in the:
/usr/share/mysql-test/suite/innodb_stress/t/load_generator.py

instead of:
/usr//mysql-test/suite/innodb_stress/t/load_generator.py

How to repeat:
Run:
[root@centos7 mysql-test]# ./mtr innodb_stress.innodb_stress 
from the /usr/share/mysql-test/ folder on CentOS 7.

Installed packages:
[root@centos7 mysql-test]# rpm -qa | grep mysql
mysql80-community-release-el7-2.noarch
mysql-community-common-5.7.26-1.el7.x86_64
mysql-community-client-5.7.26-1.el7.x86_64
mysql-community-libs-compat-5.7.26-1.el7.x86_64
mysql-community-libs-5.7.26-1.el7.x86_64
mysql-community-server-5.7.26-1.el7.x86_64
mysql-community-test-5.7.26-1.el7.x86_64
[1 Jul 2019 14:04] Hrvoje Matijakovic
Used correct name for the test (so it can be found easier in the future)
[2 Jul 2019 5:24] MySQL Verification Team
Hello Hrvoje Matijakovic,

Thank you for the report.
Imho this is duplicate of Bug #95843, please see Bug #95843

regards,
Umesh
[2 Jul 2019 9:06] Laurynas Biveinis
This does not look like a duplicate of bug 95843. That bug looks like a missing Python package, and not a bug. This one is wrong path.
[2 Jul 2019 9:42] MySQL Verification Team
Agreed, thank you for correcting.
I'll check it once again and come back on this.

regards,
Umesh
[2 Jul 2019 9:48] MySQL Verification Team
Quick check on OL7, binary tarball build doesn't have this issue:

./mtr innodb_stress.innodb_stress
Logging: ./mtr  innodb_stress.innodb_stress
MySQL Version 5.7.26
Checking supported features...
 - SSL connections supported
Collecting tests...
Checking leftover processes...
Removing old var directory...
Creating var directory '/export/umesh/server/binaries/GABuilds/mysql-5.7.26/mysql-test/var'...
Installing system database...
Using parallel: 1

==============================================================================

TEST                                      RESULT   TIME (ms) or COMMENT
--------------------------------------------------------------------------

worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 13000..13009
[100%] innodb_stress.innodb_stress              [ pass ]   1535
--------------------------------------------------------------------------
The servers were restarted 0 times
Spent 1.535 of 329 seconds executing testcases

Completed: All 1 tests were successful.
[2 Jul 2019 12:49] MySQL Verification Team
Thank you for the feed.
Observed that 5.7.26 is affected.

regards,
Umesh
[2 Jul 2019 12:49] MySQL Verification Team
Test results - 5.7.26, 8.0.16

Attachment: 96048.results (application/octet-stream, text), 7.44 KiB.