Bug 328269 – dev-util/kdevelop-4.4.1 fails tests

• Status: RESOLVED UPSTREAM
• Product: Gentoo Linux

[Description Maciej Mrozowski 2010-07-14 14:50:58 UTC]

From Markos report:

Tests fail for kdevelop

65% tests passed, 7 tests failed out of 20

Total Test time (real) =  18.18 sec

The following tests FAILED:
          6 - duchaintest (Failed)
          8 - cppcodecompletiontest (Failed)
          9 - cppcodegentest (Failed)
         16 - cmakeprojectvisitortest (Failed)
         18 - cmakeloadprojecttest (Failed)
         19 - gdbtest (Failed)
         20 - qtprinters (Failed)
Errors while running CTest

Restricting for now.

[Comment 1 Andreas K. Hüttel 2011-03-05 17:20:04 UTC]

Created attachment 264849 [details]
test log for kdevelop-4.2.0

Status as of 4.2.0: 
* 4 of 22 tests fail with X and DBUS
* Several tests bring up windows and/or start other programs, i.e. will have to be disabled

Test log attached

[Comment 2 Andreas K. Hüttel 2011-05-09 20:24:38 UTC]

*** Bug 366471 has been marked as a duplicate of this bug. ***

[Comment 3 Andreas K. Hüttel 2011-12-10 17:59:47 UTC]

4.2.3:
The following tests FAILED:
          2 - parsertest (Failed)
         10 - cppcodegentest (Failed)
         17 - cmakeprojectvisitortest (Failed)
         20 - cmakemanagertest (Failed)
         21 - gdbtest (Failed)
         22 - qtprinters (Failed)

Tests pop up dialog box.

[Comment 4 Andreas K. Hüttel 2011-12-10 18:00:24 UTC]

Created attachment 295401 [details]
test log for kdevelop-4.2.3

[Comment 5 Chris Reffett (RETIRED) 2012-03-29 14:56:43 UTC]

Created attachment 307095 [details]
kdevelop-4.3.0-lasttest.log

For 4.3.0, there are two tests that hang and timeout (I'm guessing they timeout because they say that time to completion was 1500 seconds, one looks like it failed trying to invoke knotify and I'm not sure why the other timed out). Tests that timeout are parsertest and gdbtest, and I guess they're showing as failed because they timed out. Additionally, qtprinters fails all but two of the tests, the failures have something to do with GDB. LastTest.log attached.

[Comment 6 Ian Delaney (RETIRED) 2012-03-29 16:09:54 UTC]

FAIL!  : GDBDebugger::QtPrintersTest::testQString() 'gdb.execute("print s").contains("\"test string\"")' returned FALSE. ()
   Loc: [/var/tmp/portage/dev-util/kdevelop-4.3.0/work/kdevelop-4.3.0/debuggers/gdb/printers/tests/qtprinters.cpp(93)

is suspicious.  (4.3.0-)
presumably contains("\"test string\"") reads as \test string\
It seems as if it may have regressed to a Windows folder format, instead of
/test string/. If you're keen have a closer look in qtprinters.cpp.
However, it's a test fail, and inevitably that leads to RESTRICT, doesn't it?
Curiously this test suite started out by effectively connecting to a dbus session. Wonders never cease.

[Comment 7 Andreas K. Hüttel 2012-03-29 17:03:16 UTC]

> presumably contains("\"test string\"") reads as \test string\
> It seems as if it may have regressed to a Windows folder format, instead of
> /test string/.

Ian, "\"test string\"" reads as "test string". Please first think then comment.

[Comment 8 Michael Palimaka (kensington) 2013-06-21 17:20:46 UTC]

Tests are restricted and we have decided that it's not currently useful to track this issue.