Hi, Lukas!

On Oct 13, Lukas Javorsky wrote:
> Hi Sergei,
>
> > How do these tests fail?
> For example:
> Test = encryption.corrupted_during_recovery
> Error:
> "mysqltest: At line 25: query 'INSERT INTO t1 VALUES(2)' failed: 1932:
> Table 'test.t1' doesn't exist in engine"
>
> For the full log you can view it here:
> https://kojihub.stream.rdu2.redhat.com/kojifiles/work/tasks/7208/367208/build.log

I cannot see it, the host doesn't even resolve.

Can you share the error log? it's somewhere in
var/*/mysqld.1.err and var is normally in mysql-test/
unless you used mysql-test-run.pl --vardir=xxx

> > What do you need as a reproducer, a small standalone program?
> The best way is to create some kind of script where you can see all of the
> options that are passed to the server when the service is initialized.
> And the following SQL commands that are executed to the server (or if the
> test is not executing any commands in the server, then whatever it's
> executed after the server is started).

But that's just mysql-test-run, you have it.
--verbose will show all options that are passed to the server.
var/my.cnf is the config file.

One can probably even use ltrace to get all calls into libssl.so,
but I personally haven't tried that.

Regards,
Sergei
VP of MariaDB Server Engineering
and security@mariadb.org