Details
-
Technical task
-
Resolution: Fixed
-
P3: Somewhat important
-
None
-
None
-
None
-
c66f8407a (dev), 358a5f58e (6.7)
Description
Stack traces should be enable for ubuntu-22.04-x11-tests. If it is not possible, close this ticked with a valid reason.
Example of crash can be found from here: https://coin.ci.qt.io/coin/api/log/qt/qtdeclarative/c0ae5d98cbd53d810c1be0796d5ecee987cb29a8/LinuxUbuntu_22_04x86_64LinuxUbuntu_22_04x86_64GCCqtci-linux-Ubuntu-22.04-x86_64-51-56a600Sccache_TestOnly/5fe2a25a4555500f178553d35a935c8d0921054b/test_1704015591/log.txt.gz
agent:2023/11/08 08:31:32 build.go:404: 134: PASS : tst_controls::Basic::TextArea::test_warning() agent:2023/11/08 08:31:32 build.go:404: 134: PASS : tst_controls::Basic::TextArea::cleanupTestCase() agent:2023/11/08 08:31:32 build.go:404: 134: PASS : tst_controls::Basic::TextField::initTestCase() agent:2023/11/08 08:31:32 build.go:404: 134: qt-testrunner.py INFO: Test process exited with code: -11
qt-testrunner.py prints negative exit code is when the process was interrupted by a signal. In this case, -11 corresponds to SIGSEGV, i.e. a crash.
Attachments
| For Gerrit Dashboard: QTQAINFRA-5940 | ||||||
|---|---|---|---|---|---|---|
| # | 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 |