Details
-
Suggestion
-
Resolution: Done
-
P2: Important
-
6.2
-
None
-
Android
-
3d9e56aa6c (qt/qtbase/dev) 3d9e56aa6c (qt/tqtc-qtbase/dev)
-
2021wk44POAndroid&Mobile, 2021wk46POAndroid&Mobile, 2021wk48POAndroid&Mobile, 2021wk50POAndroid&Mobile, 2022wk02FOAndroid&Automotive, 2022wk04FOAndroid&Automotive, 2022wk06FOAndroid&Automotive
Description
When a signal like Segmentation Fault or JNI exception happens while testing with ctest, the execution of the android app is stopped and the output.txt is also stopped.
In Android we can see the stacktrace using logcat, but the ctest output just shows that the test passed (if no test case failed unit then).
It is possible to see if the test is stopped midway if it does not run the cleanup phase. But when running multiple tests, this is doesn't warn that something went wrong, or what happened for the test to stop.
Attachments
Issue Links
- relates to
-
QTBUG-97695 correctly report Android test failures on crashes
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- resulted from
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
| For Gerrit Dashboard: QTBUG-97652 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 380826,26 | FatalSignalHandler: chain back to the original crash handler | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 398042,2 | Adapt QTest::FatalSignalHandler() to support sa_sigaction when available | dev | qt/qtbase | Status: MERGED | +2 | 0 |
| 398644,2 | Adapt QTest::FatalSignalHandler() to support sa_sigaction when available | 6.3 | qt/qtbase | Status: MERGED | +2 | 0 |
| 398645,3 | Adapt QTest::FatalSignalHandler() to support sa_sigaction when available | 6.2 | qt/qtbase | Status: MERGED | +2 | 0 |
| 412394,2 | FatalSignalHandler: chain back to the original crash handler | 6.3 | qt/qtbase | Status: ABANDONED | +2 | 0 |