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

Q12020 Crashing autotest: RemoteObjects - benchmarks



    • Type: Bug
    • Status: Closed
    • Priority: P1: Critical
    • Resolution: Invalid
    • Affects Version/s: 5.14
    • Fix Version/s: None
    • Component/s: Remote Objects
    • Labels:
    • Platform/s:


      This error occurs in Windows 10



      agent:2020/02/24 22:10:40 build.go:253: tst_benchmarkstest.cpp
      agent:2020/02/24 22:10:40 build.go:253: tst_benchmarkstest.cpp: fatal error C1041: cannot open program database 'C:\Users\qt\work\qt\qtremoteobjects\tests\auto\benchmarks\.obj\release\tst_benchmarkstest.vc.pdb'; if multiple CL.EXE write to the same .PDB file, please use /FS
      agent:2020/02/24 22:10:40 build.go:253: jom: C:\Users\qt\work\qt\qtremoteobjects\tests\auto\benchmarks\Makefile.Release [.obj\release\tst_benchmarkstest.obj] Error 2
      agent:2020/02/24 22:10:40 build.go:253: jom: C:\Users\qt\work\qt\qtremoteobjects\tests\auto\benchmarks\Makefile [release-check] Error 2
      agent:2020/02/24 22:10:40 build.go:304: Process finished with error: exit status 2
      agent:2020/02/24 22:10:40 build.go:529: Executing scheduled instruction 1 of 2 - Upload all core dumps if there are some
      agent:2020/02/24 22:10:40 build.go:437: Skip uploading core files because CORE_FILES_PATH is not set in the environment
      agent:2020/02/24 22:10:40 build.go:534: 
      agent:2020/02/24 22:10:40 build.go:529: Executing scheduled instruction 2 of 2 - Upload test results
      agent:2020/02/24 22:10:40 build.go:854: No test results collected
      agent:2020/02/24 22:10:40 build.go:534: 
      agent:2020/02/24 22:10:40 agent.go:272: Test failed
      agent:2020/02/24 22:10:40 agent.go:202: ERROR building: exit status 2
      INFO:workitem.py:610(14736): Agent FINISHED FAIL: testing C:/Users/qt/work/qt/qtremoteobjects/tests/auto/benchmarks: qt/qtremoteobjects/b6ef84b3546332dbda3ae5c026243b4aa486dad1/WindowsWindows_10x86_64WindowsWindows_10x86MSVC2017qtci-windows-10-x86_64-16-2a685f/b533d1759b9bf33c53574039ff31876badb02054/Test


      external log: 

      https://testresults.qt.io/ coin/api/results/qt/qtremoteobjects/b6ef84b3546332dbda3ae5c026243b4aa486dad1/WindowsWindows_10x86_64WindowsWindows_10x86MSVC2017qtci-windows-10-x86_64-16-2a685f/b533d1759b9bf33c53574039ff31876badb02054/test_1582628184/log.txt.gz


      The wanted action

      • Fix the autotest flakiness in all affected versions, not just one. 
      • Please delegate this task to a suitable developer

      Guidelines for debugging

      Please see the internal page https://intranet.qt.io/display/QTRD/Metrics+Guidelines+for+Grafana+Tool+for+Autotests+with+Issues

      How to locate the failed flaky test:

      Please open the link to the Grafana dashboard showing the failure history of the test:


      Please see the panel List of the recent flaky tests (both passed and failed). Sort it based on the results to see the failed instances. 

      Please open the links to the Coin tasks containing the logs. Please see the test section containing state "Error" and open corresponding logs. There are two versions of the links. The first one is for the Qt company internal use allowing you to re-schedule build for debugging. The second one is public, allowing only to browse the logs.

      List of the incidents: 

      More incidents can be found from:


      The Coin log shows details and the location of the error message in it. At need, the raw log can be opened to see the entire log at once. 


        No reviews matched the request. Check your Options in the drop-down menu of this sections header.



            bstottle Brett Stottlemyer
            hehalmet Heikki Halmet
            0 Vote for this issue
            2 Start watching this issue



                Gerrit Reviews

                There are no open Gerrit changes