Today I’ve filled in the midterm evaluation and continued to work on QtWebEngine to make it ::gentoo-ready. I’m pretty happy with most of the patches and I only need someone to look through them. I’ve also tested some core KDE applications.<\/p>\n
Konsole passed all tests except TerminalInterfaceTest.<\/p>\n
Looking at the test log we can see:<\/p>\n But when running bin\/TerminalInterfaceTest in a normal shell manually it passes? <\/p>\n Another package I tested was kde-apps\/ark. If using tests it depends on app-arch\/rar, which in turn depends on glibc because it’s distributed as a binary. To work around this I just removed the dep in ark’s ebuild and ran the tests, and it passed everything :). Other notable applications that have passed test suites are Dolphin and Qutebrowser (QtWebEngine browser).<\/p>\n Tomorrow I’ll continue testing packages and see if I can find a more efficient way of testing a whole group of packages like kde-apps. <\/p>\n","protected":false},"excerpt":{"rendered":" Today I’ve filled in the midterm evaluation and continued to work on QtWebEngine to make it ::gentoo-ready. I’m pretty happy with most of the patches and I only need someone to look through them. I’ve also tested some core KDE … Continue reading 17\/18 Test #16: TerminalInterfaceTest ............***Failed \u00a0\u00a0\u00a02.20 sec<\/code><\/p>\n16\/18 Testing: TerminalInterfaceTest
\n16\/18 Test: TerminalInterfaceTest
\nCommand: \"\/var\/tmp\/portage\/kde-apps\/konsole-22.04.3\/work\/konsole-22.04.3_build\/bin\/TerminalInterfaceTest\"
\n...
\nFAIL! : Konsole::TerminalInterfaceTest::testTerminalInterface() Compared values are not the same
\nActual (stateSpy.count()): 0
\nExpected (1) : 1<\/code><\/p>\n