Non-deterministic percona_heap_blob test failure
Bug #892951 reported by
Laurynas Biveinis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Medium
|
Laurynas Biveinis | ||
5.5 |
Fix Released
|
Medium
|
Laurynas Biveinis |
Bug Description
Comment:
Logfile:
CURRENT_TEST: main.percona_
--- /home/jenkins/
+++ /home/jenkins/
@@ -153,8 +153,8 @@
1
a
-hello
HELLO
+hello
HELLO MY
select c from t1 order by c;
c
@@ -163,8 +163,8 @@
a
-hello
HELLO
+hello
HELLO MY
select b from t1 order by b;
b
mysqltest: Result content mismatch
Related branches
lp:~laurynas-biveinis/percona-server/bug892951
- Alexey Kopytov (community): Approve
-
Diff: 211 lines (+26/-22)1 file modifiedpatches/memory_dynamic_rows.patch (+26/-22)
summary: |
- Nondeterministic percona_heap_blob test failure + MEMORY engine may return rows in non-deterministic order in case of + equal key comparisson |
summary: |
- MEMORY engine may return rows in non-deterministic order in case of - equal key comparisson + MEMORY engine may return rows in non-deterministic order for equal keys |
summary: |
- MEMORY engine may return rows in non-deterministic order for equal keys + Non-deterministic percona_heap_blob test failure |
To post a comment you must log in.
I have reviewed the code and did not find any apparent nondeterminism sources. Leaving this with a CI collation to see if it comes up again in the future. Also, will consider additional Valgrind annotations if applicable.