From b8fa8b9b3d108002ada5715e12e935219490270c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Vicen=C8=9Biu=20Ciorbaru?= <vicentiu@mariadb.org>
Date: Thu, 23 Jan 2025 21:45:26 +0200
Subject: [PATCH] MDEV-35921: s3.mysqldump fails in buildbot

This is a fixup for MDEV-32250, introduced via
b24ecd7ca6b5d59be524d4e6413736dc88c26ee0, the test case was not recorded
given the new mariadb-dump format.
---
 mysql-test/suite/s3/mysqldump.result | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/mysql-test/suite/s3/mysqldump.result b/mysql-test/suite/s3/mysqldump.result
index c49916d74a9..7571bb81acd 100644
--- a/mysql-test/suite/s3/mysqldump.result
+++ b/mysql-test/suite/s3/mysqldump.result
@@ -25,12 +25,14 @@ CREATE TABLE `t1` (
   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;
 #####
 # mysqldump with --copy-s3-tables=1 XML
 ###