patch 9.1.1318: tests: test_format fails

Commit: 
https://github.com/vim/vim/commit/e9a27ef37395a0130f99e21b288b7765f0e38236
Author: zeertzjq <zeert...@outlook.com>
Date:   Fri Apr 18 10:45:45 2025 +0200

    patch 9.1.1318: tests: test_format fails
    
    Problem:  tests: test_format fails (after 9.1.1314).
    Solution: Increase the string size.  Add missing test_format.res in
              NEW_TESTS_RES (zeertzjq).
    
    closes: #17144
    
    Signed-off-by: zeertzjq <zeert...@outlook.com>
    Signed-off-by: Christian Brabandt <c...@256bit.org>

diff --git a/runtime/doc/builtin.txt b/runtime/doc/builtin.txt
index 5a72e214f..4ad6b3d7d 100644
--- a/runtime/doc/builtin.txt
+++ b/runtime/doc/builtin.txt
@@ -1,4 +1,4 @@
-*builtin.txt*  For Vim version 9.1.  Last change: 2025 Mar 30
+*builtin.txt*  For Vim version 9.1.  Last change: 2025 Apr 18
 
 
                  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -8158,7 +8158,8 @@ printf({fmt}, {expr1} ...)                                
*printf()*
 <                    1.41
 
                You will get an overflow error |E1510|, when the field-width
-               or precision will result in a string longer than 6400 chars.
+               or precision will result in a string longer than 1 MB
+               (1024*1024 = 1048576) chars.
 
                                                        *E1500*
                You cannot mix positional and non-positional arguments: >
diff --git a/src/testdir/Make_all.mak b/src/testdir/Make_all.mak
index 55434b0dc..de4e30f75 100644
--- a/src/testdir/Make_all.mak
+++ b/src/testdir/Make_all.mak
@@ -434,6 +434,7 @@ NEW_TESTS_RES = \
        test_float_func.res \
        test_fnameescape.res \
        test_fold.res \
+       test_format.res \
        test_functions.res \
        test_function_lists.res \
        test_getcwd.res \
diff --git a/src/testdir/test_format.vim b/src/testdir/test_format.vim
index 785348bee..c26128893 100644
--- a/src/testdir/test_format.vim
+++ b/src/testdir/test_format.vim
@@ -334,13 +334,13 @@ func Test_printf_pos_errors()
   call v9.CheckLegacyAndVim9Failure(["call 
printf('%1$*123456789$.*987654321$d', 5)"], "E1510:")
   call v9.CheckLegacyAndVim9Failure(["call 
printf('%123456789$*1$.*987654321$d', 5)"], "E1510:")
 
-  call v9.CheckLegacyAndVim9Failure(["call printf('%1$*2$.*1$d', 5, 9999)"], 
"E1510:")
-  call v9.CheckLegacyAndVim9Failure(["call printf('%1$*1$.*2$d', 5, 9999)"], 
"E1510:")
-  call v9.CheckLegacyAndVim9Failure(["call printf('%2$*3$.*1$d', 5, 9123, 
9321)"], "E1510:")
-  call v9.CheckLegacyAndVim9Failure(["call printf('%1$*2$.*3$d', 5, 9123, 
9321)"], "E1510:")
-  call v9.CheckLegacyAndVim9Failure(["call printf('%2$*1$.*3$d', 5, 9123, 
9312)"], "E1510:")
+  call v9.CheckLegacyAndVim9Failure(["call printf('%1$*2$.*1$d', 5, 
9999999)"], "E1510:")
+  call v9.CheckLegacyAndVim9Failure(["call printf('%1$*1$.*2$d', 5, 
9999999)"], "E1510:")
+  call v9.CheckLegacyAndVim9Failure(["call printf('%2$*3$.*1$d', 5, 9999123, 
9999321)"], "E1510:")
+  call v9.CheckLegacyAndVim9Failure(["call printf('%1$*2$.*3$d', 5, 9999123, 
9999321)"], "E1510:")
+  call v9.CheckLegacyAndVim9Failure(["call printf('%2$*1$.*3$d', 5, 9999123, 
9999312)"], "E1510:")
 
-  call v9.CheckLegacyAndVim9Failure(["call printf('%1$*2$d', 5, 9999)"], 
"E1510:")
+  call v9.CheckLegacyAndVim9Failure(["call printf('%1$*2$d', 5, 9999999)"], 
"E1510:")
 endfunc
 
 func Test_printf_pos_64bit()
diff --git a/src/version.c b/src/version.c
index e6c8690d2..a095b6782 100644
--- a/src/version.c
+++ b/src/version.c
@@ -704,6 +704,8 @@ static char *(features[]) =
 
 static int included_patches[] =
 {   /* Add new patch number below this line */
+/**/
+    1318,
 /**/
     1317,
 /**/

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/vim_dev/E1u5hZt-00ABFW-10%40256bit.org.

Raspunde prin e-mail lui