Hello. I tried to ignore it and hoped people would fix it up on their own. Seems we have not build up enough social pressure yet to make that happen. :)
EFL has a failing test case which blocks all new incoming code from being actually tested on jenkins. https://build.enlightenment.org/job/changely_efl_gcc_x86_64/lastFailedBuild/artifact/src/test-suite.log But we also have a failure in EFL mingw which only shows in stable right now because the normal EFL build never comes to it (stable does as the test case was not backported). Something missing for the cursor change for mingw. https://build.enlightenment.org/job/changely_efl_stable_mingw_x86_64/lastFailedBuild/console And elm is also failing. From the output my guess is that it needs a newer efl/eolian to be deployed which is happening due to the first problem listed. https://build.enlightenment.org/job/changely_elm_gcc_x86_64/lastFailedBuild/console Having test cases fail and doing test driven development is not a bad idea but could we keep it in a branch and master working while doing it? :) regards Stefan Schmidt ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
