[Ci-reports] fail on QtBase_5.4_Integration #141

Qt Continuous Integration System ci-noreply at qt-project.org
Wed Aug 27 15:50:16 CEST 2014


Autotest `tst_qstatusbar' failed :(

  Testing tst_QStatusBar
  FAIL!  : tst_QStatusBar::QTBUG25492_msgtimeout() 't.elapsed() >= 2000' returned FALSE. (Timer was 1937)
     Loc: [tst_qstatusbar.cpp(297)]
  Totals: 9 passed, 1 failed, 0 skipped
  QtQA::App::TestRunner: test failed, running again to see if it is flaky...
  ********* Start testing of tst_QStatusBar *********
  Config: Using QtTest library 5.4.0, Qt 5.4.0 (x86_64-little_endian-lp64 shared (dynamic) debug build; by GCC 4.6.1)
  PASS   : tst_QStatusBar::initTestCase()
  PASS   : tst_QStatusBar::tempMessage()
  PASS   : tst_QStatusBar::insertWidget()
  PASS   : tst_QStatusBar::insertPermanentWidget()
  PASS   : tst_QStatusBar::setSizeGripEnabled()
  PASS   : tst_QStatusBar::task194017_hiddenWidget()
  PASS   : tst_QStatusBar::QTBUG4334_hiddenOnMaximizedWindow()
  FAIL!  : tst_QStatusBar::QTBUG25492_msgtimeout() 't.elapsed() >= 2000' returned FALSE. (Timer was 1958)
     Loc: [tst_qstatusbar.cpp(297)]
  PASS   : tst_QStatusBar::messageChangedSignal()
  PASS   : tst_QStatusBar::cleanupTestCase()
  Totals: 9 passed, 1 failed, 0 skipped
  ********* Finished testing of tst_QStatusBar *********
  QtQA::App::TestRunner: test failure could be reproduced twice consecutively
  QtQA::App::TestRunner: end tst_qstatusbar: 5 seconds, exit code 1

  Build log: http://testresults.qt-project.org/ci/QtBase_5.4_Integration/build_00141/linux-g++_developer-build_qtnamespace_qtlibinfix_Ubuntu_11.10_x64/log.txt.gz

  Tested changes (refs/builds/5.4_1409142844):
    http://codereview.qt-project.org/93084 [PS1] - QWidget::save/restoreGeometry(): Check screen size.
    http://codereview.qt-project.org/93279 [PS2] - network: Add pending close on disconnect for non-empty write buffer
    http://codereview.qt-project.org/93187 [PS1] - Micro-optimize QVector::count()
    http://codereview.qt-project.org/93113 [PS5] - Let ANGLE use multithreaded devices if necessary.



More information about the Ci-reports mailing list