Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
11.8
-
None
-
Sprint 1 (13.01.2025)
Description
s3.mysqldump fails with wrong results in new buildbot:
s3.mysqldump w11 [ retry-fail ]
|
Test ended at 2025-01-23 18:48:27
|
CURRENT_TEST: s3.mysqldump
|
--- /home/buildbot/aarch64-ubuntu-2004-debug/build/mysql-test/suite/s3/mysqldump.result 2025-01-23 18:23:54.000000000 +0000
|
+++ /home/buildbot/aarch64-ubuntu-2004-debug/build/mysql-test/suite/s3/mysqldump.reject 2025-01-23 18:48:27.545464266 +0000
|
@@ -25,12 +25,14 @@
|
PRIMARY KEY (`pk`)
|
) ENGINE=Aria DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_uca1400_ai_ci PAGE_CHECKSUM=1;
|
/*!40101 SET character_set_client = @saved_cs_client */;
|
+set autocommit=0;
|
INSERT INTO `t1` VALUES
|
(1,1),
|
(2,2),
|
(3,3),
|
(4,4);
|
ALTER TABLE `t1` ENGINE=S3;
|
+commit; |
This was introduced by: MDEV-32250, with commit b24ecd7ca6b5d59be524d4e6413736dc88c26ee0.
Attachments
Issue Links
- is caused by
-
MDEV-32250 To benefit from MDEV-515 , please make option --no-autocommit default in mysqldump from 10.6 onwards
-
- Closed
-
Activity
Transition | Time In Source Status | Execution Times |
---|
|
7m 57s | 1 |
|
11h 43m | 1 |
|
11s | 1 |
|
4s | 1 |
|
3s | 1 |
|
7s | 1 |