Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.4.0 Beta1
-
None
-
-
529491f6d (dev), 4fdef30fe (6.9), 2f69a05bd (dev), 90dcedab2 (6.8), 6ce164b3e (6.9), 38f287443 (6.8), 6763e25cb (dev), 97b41af2a (6.9), b1b7c64a3 (6.8), 2f169f9e0 (6.9.0), b5e47fa43 (6.9.0), 08325952e (dev), 1a54a0330 (dev), 5bfbc3f17 (6.9)
Description
Change https://codereview.qt-project.org/c/qt/qtdeclarative/+/408078
Job https://testresults.qt.io/coin/integration/qt/qtdeclarative/tasks/1651146260
Snippet
agent:2022/04/28 14:08:20 build.go:394: 50: PASS : tst_QQmlDebugJS::setBreakpointInJavaScript(custom / immediate)
agent:2022/04/28 14:08:21 build.go:394: 50: PASS : tst_QQmlDebugJS::setBreakpointInJavaScript(qmlscene / immediate)
agent:2022/04/28 14:23:21 build.go:253: Virtual Memory Total: 16106127360, Free:1842241536, UsedPercent:81.137365%
agent:2022/04/28 14:23:21 build.go:264: |Process|Status| CPU-%|Command
...
...
agent:2022/04/28 14:23:24 build.go:287: | 3400| R|98.685401|/Users/qt/work/qt/qtdeclarative_standalone_tests/tests/auto/qml/debugger/qqmldebugjs/tst_qqmldebugjs -o /Users/qt/work/testresults/tst_qqmldebugjs-1651154889617.xml,xml -o -,txt
It's eating 98.68% of the CPU so clearly it's spinning doing something.
Second time i see the failure recently.
Grafana says it's been happening for a year, check Crashed pane.
Doesn't seem to be a specific test case. Sometimes it spins after tst_QQmlDebugJS::setBreakpointInJavaScript, sometimes after tst_QQmlDebugJS::interrupt, sometimes after tst_QQmlDebugJS::connect
Attachments
Issue Links
- is duplicated by
-
QTBUG-101678 tst_qqmlinspector (and other tests in tests/auto/qml/debugger/) times out on macOS 12 (x86_64) in CI
-
- Closed
-
- relates to
-
QTBUG-101972 "Killed process: No output received (timeout: 15m0s seconds)" when running tst_QQmlDebugJS
-
- Closed
-
- resulted in
-
QTBUG-132697 FAIL! : tst_QQmlDebugJS::setBreakpointInScriptThatQuits(custom) 'm_process->waitForFinished()' returned FALSE.
-
- Closed
-