MySQL Bugs: #91507: mysql-test source tree is modified during cmake/make run

Bug #91507	mysql-test source tree is modified during cmake/make run
Submitted:	29 Jun 2018 22:04	Modified:	30 Jun 2018 5:41
Reporter:	Sveta Smirnova (OCA)	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Compiling	Severity:	S3 (Non-critical)
Version:	5.7.22, 8.0.11	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Originally reported at https://jira.percona.com/browse/PS-4536

If I run cmake/make commands in some empty dir I expect that cmake/make commands should create files in work dir and don't touch source tree. Currently, I see that the following files are created in source tree during cmake/make run:

    mysql-test/collections/default.release
    mysql-test/collections/default.release.done

How to repeat:
Get MySQL source tree Note, if you already have source code make sure it does not contain said files.
Create a directory
Run cmake
Check content of mysql-test/collections in the source directory

Hello Sveta,

Thank you for the report.
Noticed this after removing those files from the source tree(are available as part of mysql-boost-8.0.11.tar.gz), later cmake created in the source/mysql-test/collections/ directory.

tar -zxvf mysql-boost-8.0.11.tar.gz
cd mysql-8.0.11
rm -rf mysql-test/collections/default.release
rm -rf mysql-test/collections/default.release.done

-- Source tree - pre cmake

ls -l mysql-test/collections/default.release*
-rw-r--r--@ 1 umshastr  staff  2752 Apr  8 12:14 mysql-test/collections/default.release.in

## cmake
mkdir bld && cd bld
cmake .. -DWITH_BOOST=../boost/

-- Source tree - post cmake

ls -l mysql-test/collections/default.release*
-rw-r--r--  1 umshastr  staff  2749 Jun 30 10:44 mysql-test/collections/default.release
-rw-r--r--  1 umshastr  staff   106 Jun 30 10:44 mysql-test/collections/default.release.done
-rw-r--r--@ 1 umshastr  staff  2752 Apr  8 12:14 mysql-test/collections/default.release.in

Regards,
Umesh

Posted by developer:
 
Duplicate of bug#16083631 ?

Posted by developer:
 
I just checked 5.7 and the problem is still there (note that you need to do git status --ignored as the files are listed in .gitignore).
It is, however, a duplicate, but the base bug is itself a duplicate of bug#28341794 which is CLOSED-FIXED, but only on 8.0.