Sorry for the late response. I did not see this email for some reason. None of the test cases in testRetryDialog hit that assert on my machine. If this unit test fails on your system, can you please enable the debug area for KPasswdServer, run the unit test only for testRetryDialog only and provide the output from it? I am curious to know why it would start failing all of the sudden since nothing was changed in that code base in a very long time.
On Mon, Dec 9, 2013 at 6:35 PM, Albert Astals Cid <aa...@kde.org> wrote: > Dawit? Are you there? Or anyone? > > This is still asserting and the tagging of 4.12 is in two days, I'd prefer > not > to have to delay it because of the failing test. > > Cheers, > Albert > > El Diumenge, 24 de novembre de 2013, a les 23:26:38, Albert Astals Cid va > escriure: > > Hi Dawit, can you please have a look at kpasswdservertest? > > > > It's asserting in > > > > QFATAL : KPasswdServerTest::testRetryDialog() ASSERT: "request" in file > > > /srv/jenkins/workspace/kde-runtime_stable/kpasswdserver/kpasswdserver.cpp, > > line 1041 > > > > Looking at the code there's an "if (request)" just after the > > "Q_ASSERT(request)" so it works in release mode, but i'd like to know if > > > > a) we should fix something > > b) we should just remove the assert > > > > To get the test passing again. > > > > Cheers, > > Albert > >
