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

Mac: CI integration often fails in tst_qabstractitemview

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P0: Blocker
    • 5.3.1
    • 5.2.0 Beta1 , 5.2.1
    • GUI: Window management
    • Mac OS 10.7 & 10.8 , CLANG
    • macOS

    Description

      For example, https://codereview.qt-project.org/#change,72008 :

      FAIL!  : tst_QAbstractItemView::testClickedSignal() 'QTest::qWaitForWindowActive(&view)' returned FALSE. ()
     Loc: [tst_qabstractitemview.cpp(1528)]

      Build log: http://testresults.qt-project.org/ci/QtBase_release_Integration/build_00394/macx-clang_developer-build_qtnamespace_OSX_10.7/log.txt.gz

      https://codereview.qt-project.org/#change,75367:
      FAIL! : tst_QAbstractItemView::task221955_selectedEditor() 'QTest::qWaitForWindowActive(&tree)' returned FALSE. ()
      Loc: [tst_qabstractitemview.cpp(1211)]
      FAIL! : tst_QAbstractItemView::task200665_itemEntered() Compared values are not the same

      Build log: http://testresults.qt-project.org/ci/QtBase_release_Integration/build_00448/macx-clang_developer-build_OSX_10.8/log.txt.gz

      NOTE: There is that Persistent UI failed to open file file://localhost/Users/qt/Library/Saved%20Application%20State/@BUNDLEIDENTIFIER@.savedState/window_9.data: Permission denied (13) but it isn't the reason for the failure!

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-33959 QCursor::setPos leads to self-notification on Mac

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

          Task - A task that needs to be done. QTQAINFRA-738 Make /Users/qt/Library/Saved Application State/ folder owned by Qt, writable and emptying it

          • 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; Flaky tests; 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

              dedietri Gabriel de Dietrich (drgvond)
              kleint Friedemann Kleint
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes