Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-132070

Ubuntu 24.04 x64: Sometimes hundreds of tests failing

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • P1: Critical
    • 6.10.0 FF
    • 6.8, 6.9
    • Coin Configuration
    • None
    • 8bec383a8 (dev), 1c0406ee1 (dev), dd927a4f3 (6.9), 70b10666c (6.8), 3cbcfb2d5 (dev), ad3f5109f (6.9)

    Description

      Sometimes Ubuntu 24.04 x64 targets:

      • ubuntu-24.04-x64-x11-tests
      • ubuntu-24.04-x64-developer-build-x11-tests

      have failed with 200, 500 or even 600 failing tests with QDEBUG prints flooding in 60,000 - 80,000 lines.

      Found similar amount of failings from Ubuntu 22.04 target:

       

      More comparable tests with same failings when target has multiple tests failing:

      Testresults:

      https://testresults.qt.io/coin/integration/qt/qt5/tasks/web_qt_qt5_1733238741182 1st run for a new round - Liang
      https://testresults.qt.io/coin/integration/qt/qt5/tasks/web_qt_qt5_1733298357821 2nd run for a new round - Liang
      https://testresults.qt.io/coin/integration/qt/qt5/tasks/web_qt_qt5_1733312693998 3rd run for a new round - Liang

      https://testresults.qt.io/coin/integration/qt/qt5/tasks/web_qt_qt5_1733320551345 1st run of new PS – Liang
      https://testresults.qt.io/coin/integration/qt/qt5/tasks/web_qt_qt5_1733340592117 2nd run of new PS – Liang
      https://testresults.qt.io/coin/integration/qt/qt5/tasks/web_qt_qt5_1733392356629 3rd run of new PS – Liang
      https://testresults.qt.io/coin/integration/qt/qt5/tasks/web_qt_qt5_1733477983161 4th run of new PS – Liang

      Testresults in CI metrics:

      ci-metrics-e28093-ci-testresults?orgId=1&var-testresult_id=web_qt_qt5_1733238741182 1st run for a new round - Liang
      ci-metrics-e28093-ci-testresults?orgId=1&var-testresult_id=web_qt_qt5_1733298357821 2nd run for a new round - Liang
      ci-metrics-e28093-ci-testresults?orgId=1&var-testresult_id=web_qt_qt5_1733312693998 3rd run for a new round - Liang

      ci-metrics-e28093-ci-testresults?orgId=1&var-testresult_id=web_qt_qt5_1733320551345 1st run of new PS – Liang
      ci-metrics-e28093-ci-testresults?orgId=1&var-testresult_id=web_qt_qt5_1733340592117 2nd run of new PS – Liang
      ci-metrics-e28093-ci-testresults?orgId=1&var-testresult_id=web_qt_qt5_1733392356629 3rd run of new PS – Liang
      ci-metrics-e28093-ci-testresults?orgId=1&var-testresult_id=web_qt_qt5_1733477983161 4th run of new PS – Liang

       

      Update to description from a comment at 21.1.2025 which described found rootcause better:

      Managed to reproduce this issue in CI with debug VM, and GUI is no longer workable:

      Host logs got insight about what is causing the crash and we might have possibly found the rootcause, thanks to tosaario 

      Jan 20 23:06:32 localhost.localdomain gnome-shell[1814]: Failed to store clipboard: Format UTF8_STRING not supported
Jan 20 23:06:32 localhost.localdomain gnome-shell[1814]: meta_selection_source_memory_new: assertion 'mimetype != NULL' failed
Jan 20 23:06:32 localhost.localdomain gnome-shell[1814]: GNOME Shell crashed with signal 11
Jan 20 23:06:32 localhost.localdomain gnome-shell[1814]: == Stack trace for context 0x5fc57ca64ba0 ==
Jan 20 23:06:32 localhost.localdomain gnome-shell[1814]: #0 5fc57cb2ff38 i resource:///org/gnome/shell/ui/init.js:21 (243317d70bf0 @ 48)

      After gnome-shell crash, logs showed gnome-shell service was tried to re-start couple of times without success:

      Jan 20 23:06:36 localhost.localdomain gsd-media-keys[1957]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/Shell”
Jan 20 23:06:36 localhost.localdomain gnome-shell[1547265]: Window manager error: Another compositing manager is already running on screen 0 on display “:0”.
Jan 20 23:06:36 localhost.localdomain systemd[1225]: org.gnome.Shell@x11.service: Failed with result 'protocol'.
Jan 20 23:06:36 localhost.localdomain systemd[1225]: Failed to start org.gnome.Shell@x11.service - GNOME Shell on X11.
Jan 20 23:06:36 localhost.localdomain systemd[1225]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies.
Jan 20 23:06:36 localhost.localdomain systemd[1225]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 4.
Jan 20 23:06:36 localhost.localdomain systemd[1225]: org.gnome.Shell-disable-extensions.service - Disable GNOME Shell extensions after failure was skipped because of an unmet condition check (ConditionPathExists=/run/user/1000/gnome-shell-disable-extensions).
Jan 20 23:06:36 localhost.localdomain systemd[1225]: org.gnome.Shell@x11.service: Start request repeated too quickly.
Jan 20 23:06:36 localhost.localdomain systemd[1225]: org.gnome.Shell@x11.service: Failed with result 'protocol'.
Jan 20 23:06:36 localhost.localdomain systemd[1225]: Failed to start org.gnome.Shell@x11.service - GNOME Shell on X11.
Jan 20 23:06:36 localhost.localdomain systemd[1225]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies.
Jan 20 23:06:36 localhost.localdomain systemd[1225]: org.gnome.Shell-disable-extensions.service - Disable GNOME Shell extensions after failure was skipped because of an unmet condition check (ConditionPathExists=/run/user/1000/gnome-shell-disable-extensions).
Jan 20 23:06:37 localhost.localdomain gsd-media-keys[1957]: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed

      And after re-start failed, qtbase tests started to fail with:

      • 'QTest::qWaitForWindowActive(&window)' returned FALSE. ()
      Jan 20 23:07:25 localhost.localdomain coin-bootstrap-agent.desktop[2430]: agent:2025/01/20 23:07:25 build.go:404: ********* Start testing of tst_QShortcut *********
Jan 20 23:07:25 localhost.localdomain coin-bootstrap-agent.desktop[2430]: agent:2025/01/20 23:07:25 build.go:404: Config: Using QtTest library 6.10.0, Qt 6.10.0 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.3.0), ubuntu 24.04
Jan 20 23:07:25 localhost.localdomain coin-bootstrap-agent.desktop[2430]: agent:2025/01/20 23:07:25 build.go:404: PASS   : tst_QShortcut::initTestCase()
Jan 20 23:07:25 localhost.localdomain coin-bootstrap-agent.desktop[2430]: agent:2025/01/20 23:07:25 build.go:404: FAIL!  : tst_QShortcut::applicationShortcut() 'QTest::qWaitForWindowActive(&window)' returned FALSE. ()
Jan 20 23:07:25 localhost.localdomain coin-bootstrap-agent.desktop[2430]: agent:2025/01/20 23:07:25 build.go:404:    Loc: [/home/qt/work/qt/qtbase/tests/auto/gui/kernel/qshortcut/tst_qshortcut.cpp(38)]
Jan 20 23:07:25 localhost.localdomain coin-bootstrap-agent.desktop[2430]: agent:2025/01/20 23:07:25 build.go:404: FAIL!  : tst_QShortcut::windowShortcut() 'QGuiApplication::applicationState() == Qt::ApplicationActive' returned FALSE. ()
Jan 20 23:07:25 localhost.localdomain coin-bootstrap-agent.desktop[2430]: agent:2025/01/20 23:07:25 build.go:404:    Loc: [/home/qt/work/qt/qtbase/tests/auto/gui/kernel/qshortcut/tst_qshortcut.cpp(55)]
Jan 20 23:07:25 localhost.localdomain coin-bootstrap-agent.desktop[2430]: agent:2025/01/20 23:07:25 build.go:404: PASS   : tst_QShortcut::cleanupTestCase()
Jan 20 23:07:25 localhost.localdomain coin-bootstrap-agent.desktop[2430]: agent:2025/01/20 23:07:25 build.go:404: Totals: 2 passed, 2 failed, 0 skipped, 0 blacklisted, 20315ms
Jan 20 23:07:25 localhost.localdomain coin-bootstrap-agent.desktop[2430]: agent:2025/01/20 23:07:25 build.go:404: ********* Finished testing of tst_QShortcut *********

      Ubuntu 24.04 has gnome-shell 46.0 which has a bug which is fixed at 46.1. Bug report created by Toni, more info from there:

      By checking gnome-shell packages, it seems that Ubuntu 24.10 already has gnome-shell 47.0:

      Side notes:

      • Logs showed also
        • "Window manager error: Another compositing manager is already running on screen 0 on display “:0”."
        • "Start request repeated too quickly"
      • Not sure if those could give any workaround to recover from this, before fix is backported to Ubuntu 24.04

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-61967 Order of QWindow expose and activation not specified

          • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
          • Open

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. QTBUG-120124 Improvements to deferred deletions / deleteLater()

          • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. QTQAINFRA-6898 force the tests for Ubuntu 24.04 X11 (not InsignificantTests)

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTQAINFRA-6898 force the tests for Ubuntu 24.04 X11 (not InsignificantTests)

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Task - A task that needs to be done. QTQAINFRA-7007 Ubuntu 24.04: Upgrade Tier1 image to the newest Ubuntu 24.04.2 LTS version

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Open

          Task - A task that needs to be done. QTQAINFRA-6967 Synchronize GNOME based Linux gsettings into common script

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • In Progress

          Technical task - A technical task. QTQAINFRA-6322 Add Ubuntu 24.04 x64 to Qt 6.9 (dev)

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              teheikki Tero Heikkinen
              teheikki Tero Heikkinen
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: