KDevelop 4.7.2 released

[Milian Wolff]

On Saturday, October 17, 2015 11:47:19 AM CEST René J.V. Bertin wrote:
> On Monday October 12 2015 11:29:32 Milian Wolff wrote:
> 
> Hey
> 
> > I'm happy to announce the availability of KDevelop 4.7.2. This is a bug
> > fix
> 
> ...
> 
> > ChangeLog for kdev-python v1.7.2-py3
> > ====================================
> 
> ...
> 
> Is this expected (running the git heads of the respective branches, to be
> honest)?

I doubt failing tests are to be expected ;-)

> /opt/local/bin/ctest --force-new-ctest-process
> Test project
> /opt/local/var/macports/build/_opt_local_site-ports_kde_kdev-python/kdev-py
> thon/work/build Start 1: pyasttest
> 1/5 Test #1: pyasttest ........................   Passed    1.14 sec
>     Start 2: pycythontest
> 2/5 Test #2: pycythontest .....................   Passed    0.41 sec
>     Start 3: pyduchaintest
> 3/5 Test #3: pyduchaintest ....................***Failed   10.37 sec
>     Start 4: duchainbench
> 4/5 Test #4: duchainbench .....................   Passed    3.38 sec
>     Start 5: pycompletiontest
> 5/5 Test #5: pycompletiontest .................   Passed   12.78 sec
> 
> 80% tests passed, 1 tests failed out of 5
> 
> Total Test time (real) =  28.09 sec
> 
> The following tests FAILED:
>           3 - pyduchaintest (Failed)
> 
> Which appears to be due to
> 
> 3: XFAIL  : PyDUChainTest::testTypes(lambda) not implemented: aliasing
> lambdas 3:
> t.cpp(781)] 3: XFAIL  :
> PyDUChainTest::testCannotOverwriteBuiltins(can_have_custom) not implemented

No, these are expected failures. Look for FAIL or XPASS, or a crash.

> Also, since there's a benchmark and presuming it is intended to measure
> performance timings: how reasonable is the achieved result for a 2.7Ghz i7
> from 2011?

Most benchmarks we have are used for profiling to make things faster. We don't 
use them to profile performance across devices.

Bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de