| Bug #69105 | Flaws in binlog_server_start_options test | ||
|---|---|---|---|
| Submitted: | 30 Apr 2013 17:05 | Modified: | 30 Apr 2013 17:45 |
| Reporter: | Justin Tolmer | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | Tests: Server | Severity: | S3 (Non-critical) |
| Version: | 5.6.11 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[30 Apr 2013 17:45]
Sveta Smirnova
Thank you for the report. Verified ad described.
[17 Mar 2014 16:50]
James Page
I'd also add that this test requires a writable /usr in the instance where the test is being run against and installed server, which prevents its use by non-privileged users - and creating data in /usr is not a great idea.
[19 May 2015 7:43]
Honza Horak
Adding myself to CC, since we have hit this as well.
Description: When we encounter intermittent failures in individual tests, we often use a process of running that test in parallel and with a repeat count in order to flush out the problem. The binlog_server_start_options test has a few flaws which cause problems when run in such a manner. First, it does not support running multiple instances concurrently because it writes and removes a cnf file in a shared location. Second, the datadir it creates assumes that the server was built without specifying a default location for datadir other than 'data/'. Also, because it uses the compiled-in datadir, that also prevents it from being able to run multiple instances of the test in parallel. Finally, and possibly the worst flaw, if one does try to run multiple instances of the test in parallel, the test may end up doing a rmtree('/data'), which may be very bad if '/data' exists. How to repeat: Read the code of the test. -or- ./mtr --repeat=8 --parallel=8 binlog.binlog_server_start_options binlog.binlog_server_start_options binlog.binlog_server_start_options binlog.binlog_server_start_options binlog.binlog_server_start_options binlog.binlog_server_start_options binlog.binlog_server_start_options binlog.binlog_server_start_options