neovim

commit ca7f8786a0eb578895400e23cd21e25cc0f91800
parent e057b38e7037808b3593fb1035794595b4e4a45e
Author: Justin M. Keyes <justinkz@gmail.com>
Date:   Wed,  6 Dec 2023 08:26:30 -0800

test: unreliable 'nofsync' test #26423

Followup to 27501d3b6a8d577cf3f5ecc3fe9e219f477586b7.

Problem:
CI sometimes fails. Something is triggering an extra fsync().

    FAILED   test/functional/core/fileio_spec.lua @ 52: fileio fsync() with 'nofsync' #8304
    test/functional/core/fileio_spec.lua:100: Expected objects to be the same.
    Passed in:
    (number) 5
    Expected:
    (number) 4

Solution:
Relax the assertion.
Diffstat:
M
test/functional/core/fileio_spec.lua
 | 
7
++++---

1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/test/functional/core/fileio_spec.lua b/test/functional/core/fileio_spec.lua
@@ -89,14 +89,15 @@ describe('fileio', function()
 
     -- 2. Explicit :preserve command.
     command('preserve')
-    -- TODO: should be exactly 2; figure out where the extra fsync() is coming from. #26404
-    ok(request('nvim__stats').fsync >= 2)
+    -- TODO: should be exactly 2; where is the extra fsync() is coming from? #26404
+    ok(request('nvim__stats').fsync == 2 or request('nvim__stats').fsync == 3)
 
     -- 3. Enable 'fsync' option, write file.
     command('set fsync')
     feed('Abaz<esc>h')
     command('write')
-    eq(4, request('nvim__stats').fsync)
+    -- TODO: should be exactly 4; where is the extra fsync() is coming from? #26404
+    ok(request('nvim__stats').fsync == 4 or request('nvim__stats').fsync == 5)
     eq('foozubbaz', trim(read_file('Xtest_startup_file1')))
 
     -- 4. Exit caused by deadly signal (+ 'swapfile').