[Ci-reports] fail on ssh://codereview.qt-project.org:29418/qt/qtbase#dev

Qt Continuous Integration System ci-noreply at qt-project.org
Wed Jul 3 14:21:41 CEST 2013


Autotest `tst_qfilesystemwatcher' failed :(

The test was determined to be flaky, meaning results were not consistent across multiple runs.  This might make the problem difficult to reproduce.  Also, flaky failures might or might not be related to any recent changes in the source code.

  Testing tst_QFileSystemWatcher
  FAIL!  : tst_QFileSystemWatcher::watchFileAndItsDirectory(native backend) Compared values are not the same
     Actual   (fileChangedSpy.count()): 1
     Expected (0): 0
  .\tst_qfilesystemwatcher.cpp(460) : failure location
  Totals: 16 passed, 1 failed, 0 skipped
  QtQA::App::TestRunner: test failed, running again to see if it is flaky...
  ********* Start testing of tst_QFileSystemWatcher *********
  Config: Using QtTest library 5.2.0, Qt 5.2.0
  PASS   : tst_QFileSystemWatcher::initTestCase()
  QDEBUG : tst_QFileSystemWatcher::basicTest(native backend) QFileSystemWatcher: skipping polling engine, using only native engine
  QDEBUG : tst_QFileSystemWatcher::basicTest(native backend) QFileSystemWatcher: skipping polling engine, using only native engine
  QDEBUG : tst_QFileSystemWatcher::basicTest(native backend) QFileSystemWatcher: skipping polling engine, using only native engine
  QDEBUG : tst_QFileSystemWatcher::basicTest(native backend) QFileSystemWatcher: skipping polling engine, using only native engine
  PASS   : tst_QFileSystemWatcher::basicTest(native backend)
  QDEBUG : tst_QFileSystemWatcher::basicTest(poller backend) QFileSystemWatcher: skipping native engine, using only polling engine
  QDEBUG : tst_QFileSystemWatcher::basicTest(poller backend) QFileSystemWatcher: skipping native engine, using only polling engine
  QDEBUG : tst_QFileSystemWatcher::basicTest(poller backend) QFileSystemWatcher: skipping native engine, using only polling engine
  QDEBUG : tst_QFileSystemWatcher::basicTest(poller backend) QFileSystemWatcher: skipping native engine, using only polling engine
  PASS   : tst_QFileSystemWatcher::basicTest(poller backend)
  QDEBUG : tst_QFileSystemWatcher::watchDirectory(native backend) QFileSystemWatcher: skipping polling engine, using only native engine
  QDEBUG : tst_QFileSystemWatcher::watchDirectory(native backend) QFileSystemWatcher: skipping polling engine, using only native engine
  QSYSTEM: tst_QFileSystemWatcher::watchDirectory(native backend) QFileSystemWatcher: FindNextChangeNotification failed for "C:\users\qt\appdata\local\temp\tst_qfilesystemwatcherkobaaa\testdir"  (Access is denied.)
  PASS   : tst_QFileSystemWatcher::watchDirectory(native backend)
  QDEBUG : tst_QFileSystemWatcher::watchDirectory(poller backend) QFileSystemWatcher: skipping native engine, using only polling engine
  QDEBUG : tst_QFileSystemWatcher::watchDirectory(poller backend) QFileSystemWatcher: skipping native engine, using only polling engine
  PASS   : tst_QFileSystemWatcher::watchDirectory(poller backend)
  PASS   : tst_QFileSystemWatcher::addPath()
  PASS   : tst_QFileSystemWatcher::removePath()
  QtQA::App::TestRunner: Timed out after 450 seconds
  QtQA::App::TestRunner: test failed on first and second attempts, but with different behavior each time:
  QtQA::App::TestRunner:   first attempt:  exited with exit code 1
  QtQA::App::TestRunner:   second attempt: exited with exit code 293
  QtQA::App::TestRunner: the test seems to be flaky, please fix this
  QtQA::App::TestRunner: this flaky test is being treated as a FAIL
  QtQA::App::TestRunner: end tst_qfilesystemwatcher: 538 seconds, exit code 293

  Build log: http://testresults.qt-project.org/ci/QtBase_dev_Integration/build_01159/win64-msvc2012_developer-build_qtnamespace_Windows_8/log.txt.gz

  Tested changes (refs/builds/dev_1372847036):
    http://codereview.qt-project.org/60294 [PS1] - Xcode: Fix defines in OTHER_C/CPLUSPLUSFLAGS for project file output
    http://codereview.qt-project.org/60029 [PS6] - Xcode: Fix string quoting to match ASCII plist format



More information about the Ci-reports mailing list