Summary: | kde-base/ksystemlog-4.4.4 fails tests | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED UPSTREAM | ||
Severity: | QA | CC: | esigra, vincent |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 241922, 313999 | ||
Attachments: |
Build log
Build log including tests Test log Output of emerge --info |
Description
Diego Elio Pettenò (RETIRED)
2009-12-05 11:54:38 UTC
Created attachment 212144 [details]
Build log
What's the status with 4.3.5 or 4.4.2? All versions in tree have now RESTRICT="test" So while it's not really fixed, it's fixed somehow... Bugs with test failitures are left open even when RESTRICT=test is in place. Only proper fix can close these bugs. Status as of 4.4.3: * the tests compile now * all fail without X * using virtualx.eclass, the tests start and some pass. But, they start an entire kde session on the frame buffer, and at some point the emerge just hangs. More info on request... looks pretty hopeless imho. I have emerged kde-base/ksystemlog-4.4.4 just now, and I didn't have any problem. And the program works for me. (In reply to comment #6) > I have emerged kde-base/ksystemlog-4.4.4 just now, and I didn't have any > problem. > And the program works for me. > Did the test phase really run? You need FEATURES=test and I_KNOW_WHAT_I_AM_DOING=1 in your make.conf for the tests to run. 4.4.4 looks already much better than 4.4.3, now (even whithout X trickery) only one of 5 tests fail. Details follow in attachments. * >>> Test phase [test]: kde-base/ksystemlog-4.4.4 make -j9 -j1 test Running tests... Test project /var/tmp/portage/kde-base/ksystemlog-4.4.4/work/ksystemlog-4.4.4_build Start 1: ksystemlog-logModeFactoryTest 1/5 Test #1: ksystemlog-logModeFactoryTest ........ Passed 0.80 sec Start 2: ksystemlog-systemAnalyzerTest 2/5 Test #2: ksystemlog-systemAnalyzerTest ........***Failed 8.28 sec Start 3: ksystemlog-kernelAnalyzerTest 3/5 Test #3: ksystemlog-kernelAnalyzerTest ........ Passed 0.16 sec Start 4: ksystemlog-kioLogFileReaderTest 4/5 Test #4: ksystemlog-kioLogFileReaderTest ...... Passed 100.29 sec Start 5: ksystemlog-findIncompatibleKioTest 5/5 Test #5: ksystemlog-findIncompatibleKioTest ... Passed 0.06 sec 80% tests passed, 1 tests failed out of 5 Total Test time (real) = 109.63 sec Created attachment 235187 [details]
Build log including tests
Created attachment 235189 [details]
Test log
Created attachment 235191 [details]
Output of emerge --info
4.5.1: all tests fail :( Fixed in 4.5.3 and later Needs x, and the tests only succeed (without modifications) in 2007 !!! Grr. Not fixed yet. Something else is missing. We need a virtualdbus.eclass. "Fixed" starting 4.5.95 by disabling the one test (of 5) that always fails... (Upstream has not looked at this for at least 4 years.) |