[MDEV-4482] main.windows test fails in buildbot with result mismatch Created: 2013-05-05  Updated: 2013-05-05  Resolved: 2013-05-05

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.13

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergei Petrunia
Resolution: Fixed Votes: 0
Labels: buildbot


 Description   

http://buildbot.askmonty.org/buildbot/builders/win64-release2/builds/2621

CURRENT_TEST: main.windows
 
--- c:/buildbot/win64-release2/build/mysql-test/r/windows.result	2013-04-04 01:35:59.017999000 -0700
 
+++ c:\buildbot\win64-release2\build\mysql-test\r\windows.reject	2013-04-04 02:09:47.037573900 -0700
 
@@ -16,7 +16,7 @@
 
 INSERT INTO t1 VALUES (1,1);
 
 EXPLAIN SELECT * FROM t1 WHERE b =  (SELECT max(2));
 
 id	select_type	table	type	possible_keys	key	key_len	ref	rows	Extra
 
-1	PRIMARY	NULL	NULL	NULL	NULL	NULL	NULL	NULL	Impossible WHERE noticed after reading const tables
 
+1	PRIMARY	t1	system	NULL	NULL	NULL	NULL	1	
 2	SUBQUERY	NULL	NULL	NULL	NULL	NULL	NULL	NULL	No tables used
 
 DROP TABLE t1;
 
 CREATE DATABASE `TESTDB`;

The failure started happening with the revision 3648, which made the change in the result file:

Committer: Sergey Petrunya
 
Date: 2013-04-04 08:34:31 UTC
 
Revision ID: psergey@askmonty.org-20130404083431-f54isf947r0sbo4j
 
Update tests results, mysql-test/r/windows.result



 Comments   
Comment by Sergei Petrunia [ 2013-05-05 ]

Investigated.

The reason behind this is: Timour has pushed fix for MDEV-4482 , which changed t1:system into t1:"Impossible where".

He has pushed into 5.5. He didn't update windows.result. I saw the error in buildbot and pushed an update to windows.result. The problem is, I've pushed it into 5.3, not 5.5.

Now, I should revert that push in 5.3 and null-merge it into 5.5

Generated at Thu Feb 08 06:56:47 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.