Details
Major Description
https://buildbot.mariadb.org/#/builders/208/builds/9063
|
10.5 4b3b1eb81 |
binlog.binlog_mysqlbinlog_raw_flush 'row' w1 [ fail ]
|
Test ended at 2022-11-16 16:13:55
|
|
|
CURRENT_TEST: binlog.binlog_mysqlbinlog_raw_flush
|
/home/buildbot/amd64-ubuntu-1804-bigtest/build/client//mariadb-binlog: File '/home/buildbot/amd64-ubuntu-1804-bigtest/build/mysql-test/var/1/tmp/master-bin.000002' not found (Errcode: 2 "No such file or directory")
|
mysqltest: At line 36: exec of '/home/buildbot/amd64-ubuntu-1804-bigtest/build/client//mariadb-binlog --defaults-file=/home/buildbot/amd64-ubuntu-1804-bigtest/build/mysql-test/var/1/my.cnf --local-load=/home/buildbot/amd64-ubuntu-1804-bigtest/build/mysql-test/var/tmp/1 /home/buildbot/amd64-ubuntu-1804-bigtest/build/mysql-test/var/1/tmp/master-bin.000002 > /home/buildbot/amd64-ubuntu-1804-bigtest/build/mysql-test/var/1/tmp/local-bin.000002.out' failed, error: 256, status: 1, errno: 0
|
Output from before failure:
|
# MYSQL_BINLOG MYSQLTEST_VARDIR/tmp/master-bin.000002 > MYSQLTEST_VARDIR/tmp/local-bin.000002.out
|
|
|
|
|
|
|
The result from queries just before the failure was:
|
CREATE TABLE t1 (a int);
|
FLUSH LOGS;
|
INSERT INTO t1 VALUES (1);
|
# timeout TIMEOUT MYSQL_BINLOG --raw --read-from-remote-server --user=root --host=127.0.0.1 --port=MASTER_MYPORT --stop-never --result-file=MYSQLTEST_VARDIR/tmp/ master-bin.000001
|
# MYSQL_BINLOG MYSQLTEST_VARDIR/tmp/master-bin.000002 > MYSQLTEST_VARDIR/tmp/local-bin.000002.out
|
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Fix Version/s | 10.7 [ 24805 ] |
| Fix Version/s | 10.3 [ 22126 ] |
| Fix Version/s | 10.8 [ 26121 ] |
| Assignee | Andrei Elkin [ elkin ] | Kristian Nielsen [ knielsen ] |
Hm, don't see an easy way to make this test case loop to wait for the condition to occur. The test case actually depends on the `timeout` command killing the mariadb-binlog program, as it's testing a missing flush of output buffers (normal exit will flush buffers first). And there doesn't seem to be good tools available for mysqltest to loop, waiting for the file to have the expected contents.
I think just increasing the timeout somewhat is fine in this case. If this somehow still occurs, we can reconsider.
| Fix Version/s | 10.4.33 [ 29516 ] | |
| Fix Version/s | 10.5.24 [ 29517 ] | |
| Fix Version/s | 10.6.17 [ 29518 ] | |
| Fix Version/s | 10.11.7 [ 29519 ] | |
| Fix Version/s | 11.0.5 [ 29520 ] | |
| Fix Version/s | 11.1.4 [ 29024 ] | |
| Fix Version/s | 11.2.3 [ 29521 ] | |
| Fix Version/s | 11.3.2 [ 29522 ] | |
| Fix Version/s | 10.4 [ 22408 ] | |
| Fix Version/s | 10.5 [ 23123 ] | |
| Fix Version/s | 10.6 [ 24028 ] | |
| Fix Version/s | 10.9 [ 26905 ] | |
| Fix Version/s | 10.10 [ 27530 ] | |
| Fix Version/s | 10.11 [ 27614 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
The test runs a mariadb-binlog --read-from-remote-server and kills it (linux \`timeout\` command) after 1 second.
The test fails mostly on valgrind builder, it seems the 1 second timeout is too short there, so the expected file does not get written.