[MDEV-19455] main.dyncol failed in buildbot with extra warning "Warning_info flags: 0" Created: 2019-05-13  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Dynamic Columns, Tests
Affects Version/s: 10.3, 10.4
Fix Version/s: 10.4

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Oleksandr Byelkin
Resolution: Unresolved Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/13805

10.3 e8dd18a4

 
main.dyncol                              w3 [ fail ]  Found warnings/errors in server log file!
 
        Test ended at 2019-05-04 12:30:54
 
line
 
Warning_info  flags: 0
 
 
 
^ Found warnings in D:/win32-debug/build/mysql-test/var/3/log/mysqld.1.err
 
ok



 Comments   
Comment by Marko Mäkelä [ 2019-10-11 ]

http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/15956/steps/test/logs/stdio

10.4 09afd3da1a80e403b5375845770dde61832afa50

 
main.dyncol                              w1 [ fail ]  Found warnings/errors in server log file!
 
        Test ended at 2019-10-10 21:39:40
 
line
 
Warning_info  flags: 0
 
 
 
^ Found warnings in D:/winx64-debug/build/mysql-test/var/1/log/mysqld.1.err
 
ok

Comment by Marko Mäkelä [ 2019-10-11 ]

In the error log, I noticed that the preceding test main.drop_bad_db_type had inadvertently enabled all DBUG tracing by executing

SET debug_dbug='-d,…';

instead of following the preferred pattern of

SET @save_dbug=@@debug_dbug;
 
SET debug_dbug='+d,…';
 
…
 
SET debug_dbug=@save_dbug;

The test was introduced years ago. I searched MariaDB 5.5 for similar tests, and adjusted the main ones (notably, not --suite=rpl, because I believe that alice has been requested to do that).

Generated at Thu Feb 08 08:51:49 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.