Details
-
Bug
-
Resolution: Fixed
-
P1: Critical
-
None
-
dev
-
None
-
-
c66f8407a (dev), 358a5f58e (6.7)
Description
It tries twice to get a stacktrace, and hangs for five minutes because of that!
agent:2023/11/06 18:08:16 build.go:404: 98: FAIL! : tst_QProcess::setChildProcessModifier(normal) 'process.waitForFinished(5000)' returned FALSE. (Process operation timed out) agent:2023/11/06 18:08:16 build.go:404: 98: Loc: [/home/qt/work/qt/qtbase/tests/auto/corelib/io/qprocess/tst_qprocess.cpp(1519)] agent:2023/11/06 18:08:16 build.go:404: 98: QWARN : tst_QProcess::setChildProcessModifier(normal) QProcess: Destroyed while process ("testProcessNormal/testProcessNormal") is still running. agent:2023/11/06 18:08:46 build.go:404: 98: PASS : tst_QProcess::setChildProcessModifier(detached) agent:2023/11/06 18:13:46 build.go:404: 98: agent:2023/11/06 18:13:46 build.go:404: 98: failChildProcessModifier function time: 300000ms, total time: 351864ms agent:2023/11/06 18:13:46 build.go:404: 98: agent:2023/11/06 18:13:46 build.go:404: 98: === Stack trace === agent:2023/11/06 18:13:46 build.go:404: 98: Could not attach to process. If your uid matches the uid of the target agent:2023/11/06 18:13:46 build.go:404: 98: process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try agent:2023/11/06 18:13:46 build.go:404: 98: again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf agent:2023/11/06 18:13:46 build.go:404: 98: ptrace: Inappropriate ioctl for device. agent:2023/11/06 18:13:46 build.go:404: 98: === End of stack trace === agent:2023/11/06 18:13:46 build.go:404: 98: QFATAL : tst_QProcess::failChildProcessModifier(normal) Test function timed out agent:2023/11/06 18:13:46 build.go:404: 98: FAIL! : tst_QProcess::failChildProcessModifier(normal) Received a fatal error. agent:2023/11/06 18:13:46 build.go:404: 98: Totals: 104 passed, 2 failed, 0 skipped, 0 blacklisted, 352328ms agent:2023/11/06 18:13:46 build.go:404: 98: ********* Finished testing of tst_QProcess ********* agent:2023/11/06 18:13:46 build.go:404: 98: Received signal 6 (SIGABRT) agent:2023/11/06 18:13:46 build.go:404: 98: failChildProcessModifier function time: 300465ms, total time: 352328ms agent:2023/11/06 18:13:46 build.go:404: 98: agent:2023/11/06 18:13:46 build.go:404: 98: === Stack trace === agent:2023/11/06 18:13:46 build.go:404: 98: Could not attach to process. If your uid matches the uid of the target agent:2023/11/06 18:13:46 build.go:404: 98: process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try agent:2023/11/06 18:13:46 build.go:404: 98: again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf agent:2023/11/06 18:13:46 build.go:404: 98: ptrace: Inappropriate ioctl for device. agent:2023/11/06 18:13:46 build.go:404: 98: === End of stack trace === agent:2023/11/06 18:13:46 build.go:404: 98: qt-testrunner.py INFO: Test process exited with code: -6
EDIT: I've set the priority as P1 because of the 5 min delay on every crash.
Attachments
Issue Links
- blocks
-
QTQAINFRA-5933 Enable stack traces for crashes
- In Progress
- relates to
-
QTBUG-118443 Timeout when test abort()s and qtestlib tried to attach gdb, on emulated armv7
- Reported
For Gerrit Dashboard: QTQAINFRA-5930 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
532871,11 | Enable automatic gdb stacktrace in QTest, in case a test crashes | dev | qt/qt5 | Status: MERGED | +2 | 0 |
539691,2 | Enable automatic gdb stacktrace in QTest, in case a test crashes | 6.7 | qt/qt5 | Status: MERGED | +2 | 0 |