[MDEV-24688] galera.galera_ist_progress MTR failed: assert_grep.inc failed Created: 2021-01-26  Updated: 2022-05-03  Resolved: 2022-05-03

Status: Closed
Project: MariaDB Server
Component/s: Galera, Tests
Affects Version/s: 10.4.17
Fix Version/s: 10.4.25, 10.5.16, 10.6.8, 10.7.4, 10.8.3

Type: Bug Priority: Major
Reporter: Stepan Patryshev (Inactive) Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

ubuntu-2004


Attachments: Text File 210119_104_ES_stdout.log    
Issue Links:
Relates

 Description   

galera.galera_ist_progress failed on 10.5 ES: "assert_grep.inc failed".
It seems to be a sporadic issue and is not reproduced on BB.
The same failure was fixed recenetly for 10.5 ES in MENT-986.

stdio.log:

10.4.17-10, d434dab0139ae1e409ab6c87638f027105fbd911, ubuntu-2004

galera.galera_ist_progress 'innodb'      w1 [ fail ]
        Test ended at 2021-01-19 13:05:39
 
CURRENT_TEST: galera.galera_ist_progress
mysqltest: In included file "./include/assert_grep.inc": 
included from /home/jenkins/workspace/10.4e-MTR-GALERA/BuildType/Debug/label/ubuntu-2004/mysql-test/suite/galera/t/galera_ist_progress.test at line 69:
At line 152: assert_grep.inc failed.
 
The result from queries just before the failure was:
< snip >
INSERT INTO t1 VALUES (6);
INSERT INTO t1 VALUES (7);
INSERT INTO t1 VALUES (8);
INSERT INTO t1 VALUES (9);
INSERT INTO t1 VALUES (10);
connection node_2;
SET GLOBAL wsrep_provider_options = 'gmcast.isolate = 0';
connection node_1;
connection node_2;
connection node_1;
include/assert_grep.inc [Receiving IST: 13 writesets, seqnos 3-15]
include/assert_grep.inc [Receiving IST\.\.\.  0\.0% \( 0/13 events\) complete]
include/assert_grep.inc failed!
assert_text: 'Receiving IST\.\.\.  0\.0% \( 0/13 events\) complete'
assert_file: '/var/tmp/mtr/1/log/mysqld.2.err'
assert_select: 'Receiving IST\.\.\.  0\.0% \( 0/13 events\) complete'
assert_match: ''
assert_count: '1'
assert_only_after: 'Need state transfer'
number of matching lines: 2



 Comments   
Comment by Ramesh Sivaraman [ 2022-04-28 ]

This issue is still reproduced on the latest CS 10.4 build on the local machine

Generated at Thu Feb 08 09:31:55 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.