From 02a4003dc76ea5554096b1d5c7e7f07cc28d9e8b Mon Sep 17 00:00:00 2001 From: Andrew McDonnell Date: Sat, 29 Jun 2013 01:11:20 +0930 Subject: [PATCH] Added bug ref to test --- mysql-test/suite/oqgraph/boundary_conditions.test | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/mysql-test/suite/oqgraph/boundary_conditions.test b/mysql-test/suite/oqgraph/boundary_conditions.test index 5c32682caa6..c8f7c250f28 100644 --- a/mysql-test/suite/oqgraph/boundary_conditions.test +++ b/mysql-test/suite/oqgraph/boundary_conditions.test @@ -46,7 +46,7 @@ INSERT INTO graph_base(from_id, to_id) VALUES (3,4), (4,3); INSERT INTO graph_base(from_id, to_id) VALUES (5,6), (6,5); --echo # No Search/0 - result should return same rows as inserted for origid,destid,weight ---echo # FIXME - THIS CODE IS CURRENTLY BROKEN +--echo # FIXME - THIS CODE IS CURRENTLY BROKEN - see https://bugs.launchpad.net/oqgraph/+bug/1195778 SELECT * FROM graph WHERE latch='no_search'; SELECT * FROM graph WHERE latch='no_search' and destid=2 and origid=1; SELECT * FROM graph WHERE latch='no_search' and origid=1; @@ -148,6 +148,7 @@ FLUSH TABLES; TRUNCATE TABLE graph_base; #-- Uncomment the following after fixing https://bugs.launchpad.net/oqgraph/+bug/xxxxxxx - Causes the later select to not fail! +#-- For now dont report a separate bug as it may be a manifestation of https://bugs.launchpad.net/oqgraph/+bug/1195735 #-- FIXME SELECT * FROM graph; #-- Expect error if we pull the table out from under