[MDEV-20143] innodb.innodb-virtual-columns-debug failed in buildbot with wrong result Created: 2019-07-23  Updated: 2019-09-17  Resolved: 2019-09-17

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Tests, Virtual Columns
Affects Version/s: 10.2, 10.3, 10.4, 10.5
Fix Version/s: 10.2.28, 10.3.19, 10.4.9

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Nikita Malyavin
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-17005 ASAN heap-use-after-free in innobase_... Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/14824

10.2 97055e6b11508b53203aaadfe4618f54

innodb.innodb-virtual-columns-debug 'innodb' w2 [ fail ]
        Test ended at 2019-07-23 15:06:47
 
CURRENT_TEST: innodb.innodb-virtual-columns-debug
--- D:/winx64-debug/build/src/mysql-test/suite/innodb/r/innodb-virtual-columns-debug.result	2019-07-23 14:42:35.254994000 +0000
+++ D:\winx64-debug\build\src\mysql-test\suite\innodb\r\innodb-virtual-columns-debug.reject	2019-07-23 15:06:46.939562100 +0000
@@ -9,8 +9,6 @@
 SET debug_sync= "ib_open_after_dict_open SIGNAL another_open";
 SELECT a FROM t1;
 a
-NULL
-NULL
 connection con1;
 disconnect con1;
 connection default;
 
mysqltest: Result length mismatch



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

The test was originally added by nikitamalyavin in a change that effectively added a DEBUG_SYNC point related to MDEV-17005. I moved the test to a separate file, because the addition would prevent the original test from running on non-debug servers.

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