Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.3.0, 5.4.0
-
None
-
0d3dc8c9e4ee07895c952d48faa55cf4f4b00b7b
Description
See:
http://testresults.qt-project.org/ci/QtDeclarative_dev_Integration/build_01469/linux-g++_developer-build_OpenSuSE_13.1_x64/log.txt.gz
http://testresults.qt-project.org/ci/QtDeclarative_stable_Integration/build_02121/linux-g++_developer-build_OpenSuSE_13.1_x64/log.txt.gz
One thing I can imagine is that the scenegraph kicks in before Component.onCompleted in the javascript test and paints a frame. On a threaded render loop this typlically results in 7 scenegraph events and a 1 frame paint event. However, if everything is offset by 8 events then event 32 should still not be a QQmlProfilerClient::HandlingSignal. Also, does that OpenSuSE actually do threaded rendering?
Attachments
For Gerrit Dashboard: QTBUG-39169 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
86001,2 | Record synchronous and asynchronous events separately in profiler test | stable | qt/qtdeclarative | Status: MERGED | +2 | 0 |
86553,1 | Dump all received messages if tst_QQmlProfilerService fails | stable | qt/qtdeclarative | Status: MERGED | +2 | 0 |
86619,1 | Log (the test's) clock type if qqmlprofilerservice test fails | stable | qt/qtdeclarative | Status: ABANDONED | 0 | 0 |
86624,1 | Record synchronous and asynchronous events separately in profiler test | dev | qt/qtdeclarative | Status: ABANDONED | -1 | 0 |
86625,1 | Dump all received messages if tst_QQmlProfilerService fails | dev | qt/qtdeclarative | Status: ABANDONED | -1 | 0 |
86702,1 | Keep QML and JS messages separate in QQmlProfilerService test | stable | qt/qtdeclarative | Status: MERGED | +2 | 0 |