Hello. On 21/03/16 16:26, Mike Blumenkrantz wrote: > The Enlightenment build hasn't updated in over a week; the page says that > something is not configured. Are you aware of this?
The not fully configured part is something you can ignore here. We do not have components setup neither a modeling file. Both are not needed for the normal operation and it works like this since we started with Coverity. Now back to the question why the build have not been updated since the 13th. There are three possible options why a new build gets not in every night: 1) The project reached the maximum number of builds per week already. This is based on the size of the project. With 280K lines of code E is allowed 8 builds per week (this was less before) so we normally should not see this problem for the one build per night setup we have. 2) Coverity scan service has problems and does not accept builds. 3) The E nightly build was never run. This could be because a) one of the nightly builds triggering the E nightly build failed (efl or elm) or b) because the E nightly build itself failed. Looking at the E nightly trigger build it is clear that the reason here is 3a as the build did not run since the 13th. https://build.enlightenment.org/view/Nightly/job/nightly_e_trigger/ The nightly build for efl and elm have been making trouble lately. I manually started a e nightly now. Hopefully this will get through. regards Stefan Schmidt ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel