• Bug#1102308: neovim-qt: FTBFS: flaky tests

    From Santiago Vila@21:1/5 to All on Mon Apr 7 15:30:02 2025
    Package: src:neovim-qt
    Version: 0.2.19-1
    Severity: important
    Tags: ftbfs trixie sid

    Dear maintainer:

    During a rebuild of all packages in unstable, your package failed to build:

    [ please read the notes at the end ]

    --------------------------------------------------------------------------------
    [...]
    4/20 Test #4: tst_encoding ..................... Passed 0.05 sec
    Start 5: tst_msgpackiodevice
    5/20 Test #5: tst_msgpackiodevice .............. Passed 0.04 sec
    Start 6: tst_shell
    6/20 Test #6: tst_shell ........................***Failed 4.39 sec ********* Start testing of NeovimQt::TestShell *********
    Config: Using QtTest library 5.15.15, Qt 5.15.15 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 14.2.0), debian unknown
    PASS : NeovimQt::TestShell::initTestCase()
    QWARN : NeovimQt::TestShell::benchStart() QProcess: Destroyed while process ("nvim") is still running.
    [...]
    Total Test time (real) = 36.51 sec

    The following tests FAILED:
    6 - tst_shell (Failed)
    Errors while running CTest
    FAILED: CMakeFiles/test.util
    cd /<<PKGBUILDDIR>>/build && /usr/bin/ctest --force-new-ctest-process
    ninja: build stopped: subcommand failed.
    dh_auto_test: error: cd build && LC_ALL=C.UTF-8 MESON_TESTTHREADS=1 ninja test returned exit code 1
    make[1]: *** [debian/rules:39: override_dh_auto_test] Error 25
    make[1]: Leaving directory '/<<PKGBUILDDIR>>'
    make: *** [debian/rules:21: binary] Error 2
    dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 --------------------------------------------------------------------------------

    The above is just how the build ends and not necessarily the most relevant part.
    If required, the full build log is available here:

    https://people.debian.org/~sanvila/build-logs/202503/

    About the archive rebuild: The build was made on virtual machines from AWS, using sbuild and a reduced chroot with only build-essential packages.

    In this particular case, the build was made on AWS machines of type
    m7a.medium and r7a.medium. Incidentally, those machines have a single CPU,
    but at this point it's not clear yet if that's the condition which triggers
    the build failure or, for example, the fact that they are overall slower
    than other instance types, or maybe some other reason.

    If you could not reproduce the bug using GRUB_CMDLINE_LINUX="nr_cpus=1"
    please contact me privately, as I am willing to provide ssh access to a
    virtual machine where the bug is fully reproducible.

    Disclaimer: Please note that this is probably a violation of
    Debian Policy 4.2, and the only reason I'm initially reporting
    it as "important" is to avoid discussing about the severity.

    If this is really a bug in one of the build-depends, please use
    reassign and add an affects on src:neovim-qt, so that this is still
    visible in the BTS web page for this package.

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Santiago Vila@21:1/5 to All on Sun May 11 22:10:01 2025
    severity 1102308 normal
    thanks

    Update:

    When using the kernel of trixie, the failure rate
    (on the systems where it used to fail all the time)
    becomes a lot smaller (around 5%).

    (So I can remove the package from my list of "always fails"
    and put it in the "randomly fails").

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)