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

Q12020 Crashing autotest: QtQuickcontrols - controls

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P1: Critical
    • Resolution: Won't Do
    • Affects Version/s: 6.0
    • Fix Version/s: None
    • Component/s: Quick: Controls 1
    • Labels:
      None

      Description

      This error occurs in Ubuntu_18_04 and dev

      http://coin/coin/integration/qt/qtquickcontrols/tasks/1581386770

      http://coin/coin/api/results/qt/qtquickcontrols/803aa6ce8acef25f49ded68015d8c5283e6b8e39/LinuxUbuntu_18_04x86_64LinuxQEMUarmv7GCCqtci-linux-Ubuntu-18.04-x86_64-d4fa8dUseLegacyInstructions/34e7437746a6bdfbdfc8beac8ecf96543d76df2c/test_1581387551/log.txt.gz

      agent:2020/02/11 02:38:36 build.go:220: qemu-arm: /tmp/tmp.gAyELIlEi0/translate-all.c:175: tb_lock: Assertion `!have_tb_lock' failed.
      agent:2020/02/11 02:38:36 build.go:220: qemu-arm: /tmp/tmp.gAyELIlEi0/translate-all.c:175: tb_lock: Assertion `!have_tb_lock' failed.
      agent:2020/02/11 02:38:36 build.go:220: Makefile:332: recipe for target 'check' failed
      agent:2020/02/11 02:38:36 build.go:220: make: *** [check] Error 127
      agent:2020/02/11 02:38:36 build.go:253: Process finished with error: exit status 2
      agent:2020/02/11 02:38:36 build.go:223: Error reading from stdout/err: exit status 2
      agent:2020/02/11 02:38:36 build.go:471: Executing scheduled instruction 1 of 2 - Upload all core dumps if there are some
      agent:2020/02/11 02:38:36 build.go:384: Skip uploading core files because CORE_FILES_PATH is not set in the environment
      agent:2020/02/11 02:38:36 build.go:473: 
      agent:2020/02/11 02:38:36 build.go:471: Executing scheduled instruction 2 of 2 - Upload test results
      agent:2020/02/11 02:38:36 storageclient.go:451: Collecting test results, archiving and uploading them
      agent:2020/02/11 02:38:36 result.go:177: Collecting 1 test results ...
      agent:2020/02/11 02:38:36 build.go:473: 
      agent:2020/02/11 02:38:36 agent.go:272: Test failed
      agent:2020/02/11 02:38:36 agent.go:200: ERROR building: error unmarshalling testlib xml output ('/home/qt/work/testresults/tests/auto/controls021836961'): 'XML syntax error on line 1617: unexpected EOF'.

       

      external log: 

      https://testresults.qt.io/coin/api/results/qt/qtquickcontrols/803aa6ce8acef25f49ded68015d8c5283e6b8e39/LinuxUbuntu_18_04x86_64LinuxQEMUarmv7GCCqtci-linux-Ubuntu-18.04-x86_64-d4fa8dUseLegacyInstructions/34e7437746a6bdfbdfc8beac8ecf96543d76df2c/test_1581387551/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:

      https://testresults.qt.io/grafana/d/HrvHJIEWz/03-qt-framework-please-fix-these-crashing-tests?orgId=1&from=now-30d&to=now&var-branch=dev&var-project=qt%2Fqtquickcontrols&var-testcase=tests%2Fauto%2Fcontrols

      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:

      https://testresults.qt.io/grafana/d/HrvHJIEWz/03-qt-framework-please-fix-these-crashing-tests?orgId=1&from=now-30d&to=now&var-branch=dev&var-project=qt%2Fqtquickcontrols&var-testcase=tests%2Fauto%2Fcontrols

      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. 

        Attachments

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

          Activity

            People

            Assignee:
            vhilshei Volker Hilsheimer
            Reporter:
            hehalmet Heikki Halmet
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Gerrit Reviews

                There are no open Gerrit changes