Bug #33036 ndb_update_no_read test is non-deterministic
Submitted: 6 Dec 2007 11:59
Reporter: Stewart Smith Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:mysql-5.1-telco-6.3 OS:Any
Assigned to: CPU Architecture:Any
Triage: Triaged: D3 (Medium)

[6 Dec 2007 11:59] Stewart Smith
Description:
Pushbuild shows occational test failures like this:
*** /data0/pushbuild/pb/mysql-5.1-telco-6.3/113/mysql-5.1.22-ndb-6.3.7-pb113/mysql-test/suite/ndb/r/ndb_update_no_read.result	Thu Dec  6 11:07:09 2007
--- /data0/pushbuild/pb/mysql-5.1-telco-6.3/113/mysql-5.1.22-ndb-6.3.7-pb113/mysql-test/suite/ndb/r/ndb_update_no_read.reject	Thu Dec  6 13:31:25 2007
***************
*** 153,159 ****
  affected rows: 2
  info: Rows matched: 2  Changed: 2  Warnings: 0
  @ndb_execute_count:=VARIABLE_VALUE-@ndb_init_execute_count
! 4
  affected rows: 1
  select * from t1 where a = 3 or b = 7 order by a;
  a	b	c
--- 153,159 ----
  affected rows: 2
  info: Rows matched: 2  Changed: 2  Warnings: 0
  @ndb_execute_count:=VARIABLE_VALUE-@ndb_init_execute_count
! 3
  affected rows: 1
  select * from t1 where a = 3 or b = 7 order by a;
  a	b	c
-------------------------------------------------------

How to repeat:
see pushbuild logs for 5.1-telco-6.3

Suggested fix:
determinism
[3 Feb 2008 13:02] Jonas Oreland
i removed this part of the test from pushbuild
lowering prio