| Summary: | Some tests fail on OSX/CI | ||
|---|---|---|---|
| Product: | [Developer tools] kdevplatform | Reporter: | Marko Käning <mk-lists> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | git master | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
build log
Test results separately |
||
Created attachment 89891 [details]
build log
Created attachment 89892 [details]
Test results separately
Are these test results detailed enough, or do I need to add the "-V" option to ctest? This time obviously NO crash logs appeared, as I had reported in my KDevelop ML post: http://mail.kde.org/pipermail/kdevelop/2014-December/018620.html But I have a snapshot of the OSX/CI VM's state and could deliver the crash logs mentioned in there, together with build log and test results. (But I think that the build log alone should be sufficient.) Ah, here the test results are also bigger than the build log, so it probably makes sense to upload both?! This ticket is outdated due to the OSX/CI system not active anymore the way it operated here. |
Tests have been carried out on my OSX/CI system and failed for these: --- 71% tests passed, 14 tests failed out of 48 Total Test time (real) = 752.74 sec The following tests FAILED: 9 - test_projectmodel (OTHER_FAULT) 14 - test_backgroundparser (Failed) 17 - test_templateclassgenerator (Failed) 18 - test_templatesmodel (Failed) 20 - test_uicontroller (Timeout) 21 - test_shellbuddy (Timeout) 23 - test_projectcontroller (Timeout) 24 - test_sessioncontroller (Failed) 25 - test_plugincontroller (Failed) 42 - test_projectload (Timeout) 43 - test_standardoutputview (Timeout) 44 - test_quickopen (Failed) 46 - test_kdevgit (Failed) 47 - testgenerationtest (Failed) --- Will append build log and test results. Reproducible: Always