[MDEV-16652] heap.heap_auto_increment, main.auto_increment fail, maria.maria-autoinc in buildbot with out-of-range error Created: 2018-06-30  Updated: 2018-07-25  Resolved: 2018-07-25

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2, 10.3
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Alexander Barkov
Resolution: Cannot Reproduce Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-15352 AUTO_INCREMENT breaks after updating ... Closed
relates to MDEV-16534 PPC64: Unexpected error with a negati... Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-deb-xenial-aarch64/builds/448

10.3 46857a860c90a643a8859e1bea81c727

heap.heap_auto_increment                 w3 [ fail ]
        Test ended at 2018-06-30 12:42:55
 
CURRENT_TEST: heap.heap_auto_increment
mysqltest: In included file "./include/autoinc_mdev15353.inc": 
included from /usr/share/mysql/mysql-test/suite/heap/heap_auto_increment.test at line 43:
At line 21: query 'CALL autoinc_mdev15353_one(@engine, 'tinyint')' failed: 167: Out of range value for column 'id' at row 1
 
The result from queries just before the failure was:
< snip >
#
SET @engine='MEMORY';
CREATE PROCEDURE autoinc_mdev15353_one(engine VARCHAR(64), t VARCHAR(64))
BEGIN
DECLARE query TEXT DEFAULT 'CREATE TABLE t1 ('
                             '  id TTT NOT NULL AUTO_INCREMENT,'
                             '  name CHAR(30) NOT NULL,'
                             '  PRIMARY KEY (id)) ENGINE=EEE';
EXECUTE IMMEDIATE REPLACE(REPLACE(query,'TTT', t), 'EEE', engine);
SHOW CREATE TABLE t1;
INSERT INTO t1 (name) VALUES ('dog');
SELECT * FROM t1;
UPDATE t1 SET id=-1 WHERE id=1;
SELECT * FROM t1;
INSERT INTO t1 (name) VALUES ('cat');
SELECT * FROM t1;
DROP TABLE t1;
END;
$$
CALL autoinc_mdev15353_one(@engine, 'tinyint');
 
More results from queries before failure can be found in /dev/shm/var/3/log/heap_auto_increment.log
 
Warnings from just before the error:
Error 167 Out of range value for column 'id' at row 1



 Comments   
Comment by Alexander Barkov [ 2018-07-03 ]

The problem should be gone when MDEV-16534 gets merged.

Comment by Alexander Barkov [ 2018-07-25 ]

No failures after the merge.

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