Running 3000 robot tests should not result in a log.html file of 150MB++

[GoogleCodeExporter]

Hi there,

The log writer should chapter the log.html file if the size is above say
5MB. In one stress test with 3500 test cases (only 150 passed) the
resulting log.html was 152MB long and cannot be viewed. Actually it blows
up the browser.

I've attached the  zipped log file, in case you want to see a browser
blowing up.

Original issue reported on code.google.com by kai.hack...@gmail.com on 2 Feb 2010 at 3:31

Attachments:

• log.7z

[GoogleCodeExporter]

This is a know problem and we even have a feature that allows splitting the log 
file:
http://robotframework.googlecode.com/svn/tags/robotframework-2.1.2/doc/userguide
/RobotFrameworkUserGuide.html#splitting-outputs

If splitting doesn't help, you could change keywords that log a lot to write 
their
information into external files and link them from the log file. 

There might be other workarounds too but I cannot help much more without 
knowing more
about the context. Such discussions belong to the mailing lists, though, 
instead of
this tracker.

Let us know if you have some concrete ideas on how to resolve this problem. 
Otherwise
this issue will be closed.

Original comment by pekka.klarck on 2 Feb 2010 at 9:24

[GoogleCodeExporter]

Hi, thanks for this information, it is solving the 150MB problem by splitting 
into 2
75MB problems :)

What I'm currently testing is a suite with a data-driven test that comes in 970
variations. Selenium based, and selenium is logging the page html into the log 
if it
isn't happy.

So in this case a log splitting level for each test case (4?) would be required.

Original comment by kai.hack...@gmail.com on 3 Feb 2010 at 12:50

[GoogleCodeExporter]

If you can name SeleniumLibrary keywords that produce excess output to log, 
please
submit enhancement request to SeLib's tracker to either reduce the output or 
make it
configurable.

Splitting outputs from the test level is not possible with `--splitoutputs` 
because
test suite is the smallest entity the framework handles. Changing this would be
rather big task. 

Original comment by pekka.klarck on 3 Feb 2010 at 7:40

[GoogleCodeExporter]

Output can be reduced by configuring a higher log threshold, for example with
--loglevel WARN or BuiltIn keyword Set Log Level.

Original comment by janne.t....@gmail.com on 24 Feb 2010 at 1:51

• Changed state: WontFix