Summary: | kde-base/kmail-4.7.3 tests hang | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Paweł Hajdan, Jr. (RETIRED) <phajdan.jr> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | creffett, esigra |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 241922 | ||
Attachments: |
build.log.gz
ebuild patch test patch, kmail-test.patch the Test log for the build kmail-4.8.0-test.patch 4.8.0 test log |
Description
Paweł Hajdan, Jr. (RETIRED)
2011-12-04 15:47:30 UTC
Restricting this based on your info (my 4.7.3 test box runs old pim) Here we go again. gentoo64 kmail # ebuild kmail-4.7.3.ebuild clean test Test project /mnt/gen2/tmpdir/portage/kde-base/kmail-4.7.3/work/kmail-4.7.3_build Start 1: conflictresolvertest. The dbus dilemma I suspect. How many kde packages have they copied this into? grief. Created attachment 299639 [details, diff]
ebuild patch
patch for 4.7.3 but can be adapted to others. Have left the bash line that invokes a dbus session in place but commented out.
Created attachment 299643 [details, diff]
test patch, kmail-test.patch
This simply deletes the failing tests. Now it's not clear if this is valid for all of the deleted tests in kmail. Seeing that the dbus session is sought and never connected to makes it completely ambiguous. These remaining tests do pass despite also citing what it wrongly reports as the absent dbus session. What allows one to continue and pass and the others to go belly up I don't know.
Two of these tests are (sensibly) deleted because they call a dialog box demanding passphrase keys to present crypto keys which have already been declared unwanted and troublesome.
For those who can extract these tests and run them in a home folder or wherever, that can at least delineate test .cpp files with sensible data and with wrong data that dooms it to failure. It's a start at least.
Created attachment 299651 [details]
the Test log for the build
This is the Test log showing it passing.
# gentoo64 kde-base # ebuild kmail-4.7.3.ebuild test
100% tests passed, 0 tests failed out of 22
Total Test time (real) = 7.37 sec
* Tests succeeded.
Will wonders never cease?
The use of kde4_add_unit_test will undoubtedly be found and used in other kde packages which fail tests, but for kmail here it is only used in about 2 out of the remaining 22 tests. Selecting and deleting the individual tests is as easy as pie. The hard part is assessing which are justified deletions. But here at least is a test phase that can pass.
Created attachment 300895 [details, diff]
kmail-4.8.0-test.patch
I put together a new version of the test removal patch for 4.8.0. Unfortunately, a lot more tests hang this time around, but this removed all hanging tests for me and left me with 15 tests total.
Created attachment 300897 [details]
4.8.0 test log
Output of the tests that didn't hang. Two tests failed, messagecomposer-mainjobtext and messagelist-itemsizetest, not really sure how to resolve them at present.
Tests are restricted and we have decided that it's not currently useful to track this issue. |