Bug confirmed still present even if per-run (per-mysqld if you will) directories are used:
2013-03-16 09:09:34 7f303a4f4700 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
2013-03-16 09:09:34 7f303a4f4700 InnoDB: File name /tmp/1363414156674129979/ib_log_archive_0000000000045568
2013-03-16 09:09:34 7f303a4f4700 InnoDB: File operation call: 'open' returned OS error 71.
2013-03-16 09:09:34 7f303a4f4700 InnoDB: Cannot continue operation.
2013-03-16 09:09:34 7f303a4f4700 InnoDB: Assertion failure in thread 139845113431808 in file os0file.cc line 662
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
Note the "/tmp/1363414156674129979" directory - this a nanosecond epoch generated exclusively for this run. (RQG was updated to include this new functionality to support testing all parameters in this feature better)
Bug confirmed still present even if per-run (per-mysqld if you will) directories are used:
2013-03-16 09:09:34 7f303a4f4700 InnoDB: Operating system error number 2 in a file operation. 674129979/ ib_log_ archive_ 000000000004556 8
InnoDB: The error means the system cannot find the path specified.
2013-03-16 09:09:34 7f303a4f4700 InnoDB: File name /tmp/1363414156
2013-03-16 09:09:34 7f303a4f4700 InnoDB: File operation call: 'open' returned OS error 71.
2013-03-16 09:09:34 7f303a4f4700 InnoDB: Cannot continue operation.
2013-03-16 09:09:34 7f303a4f4700 InnoDB: Assertion failure in thread 139845113431808 in file os0file.cc line 662
InnoDB: Failing assertion: 0
InnoDB: We intentionally generate a memory trap.
Note the "/tmp/136341415 6674129979" directory - this a nanosecond epoch generated exclusively for this run. (RQG was updated to include this new functionality to support testing all parameters in this feature better)