Hello. Beber, Daniel Willmann and myself have been wondering and lately chasing the grow of disk usage on jenkins. It was slow to begin with 130 MB instead of 50 for a elm nightly build but it was skyrocking over the last days with 4GB right now.
beber figured out which files are eating all the space and looking into them made it all very clear. we have debug enabled on jenkins as we often only have the logfile to trace a problem. We are well aware that the log size grows with it but it was always acceptable. This changed with the integration of eolian which gives us now a handy 3.8GB log file with 41 million lines. Dominated by things like: DBG<24905>:eo_toknz lib/eolian/eo_lexer.rl:396 eo_tokenizer_mem_walk() DBG<24907>:eo_toknz lib/eolian/eo_lexer.rl:391 eo_ tokenizer_mem_walk() DBG<24906>:eo_toknz lib/eolian/eo_lexer.rl:386 eo_tokenizer_mem_walk() save token[315] 0x7fb3ee4ea7d2 @save line[305] 18 I don't see anybody debugging this :) Could you folks tune down the noise of debugging to something useful? I know finding the balance for what is really needed it sometimes tricky but nobody will ever read all this lines and use it for debugging. :) regards Stefan Schmidt ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
