Created attachment 550980 [details] build.log > >>> Test phase: dev-util/kdevelop-php-5.2.4-r1 > * Scanning for an open DISPLAY to start Xvfb ... > * Starting Xvfb on $DISPLAY=0 ... > >>> Working in BUILD_DIR: "/var/tmp/portage/dev-util/kdevelop-php-5.2.4-r1/work/kdevelop-php-5.2.4_build" > ctest -j 5 --test-load 7.95 -E (completionbenchmark|duchain_multiplefiles) > Invalid value for 'Test Load' : 7.95 > Test project /var/tmp/portage/dev-util/kdevelop-php-5.2.4-r1/work/kdevelop-php-5.2.4_build > Start 1: lexertest > Start 2: duchain > Start 3: expressionparser > Start 4: uses > Start 5: completiontest > 1/5 Test #1: lexertest ........................ Passed 3.32 sec > 2/5 Test #5: completiontest ...................***Failed 4.26 sec > 3/5 Test #2: duchain ..........................***Failed 4.34 sec > 4/5 Test #4: uses .............................***Failed 4.30 sec > 5/5 Test #3: expressionparser .................***Failed 4.32 sec > > 20% tests passed, 4 tests failed out of 5 > > Total Test time (real) = 4.36 sec > > The following tests FAILED: > 2 - duchain (Failed) > 3 - expressionparser (Failed) > 4 - uses (Failed) > 5 - completiontest (Failed) > Errors while running CTest >
Created attachment 550982 [details] LastTest.log
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5284a79926734b4dcae1362c9d64588054755a54 commit 5284a79926734b4dcae1362c9d64588054755a54 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2018-10-13 19:14:59 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2018-10-13 19:14:59 +0000 dev-util/kdevelop-php: Restrict remaining tests... Closes: https://bugs.gentoo.org/668530 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> Package-Manager: Portage-2.3.51, Repoman-2.3.11 dev-util/kdevelop-php/kdevelop-php-5.2.4-r1.ebuild | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
(tests had been restricted in 5.2.3 already, but there we did not try to make them work in the first place...)
*** Bug 682274 has been marked as a duplicate of this bug. ***
