I've solved it right now by linking selenium.log to dev/null
Am Freitag, 15. Februar 2013 17:43:41 UTC+1 schrieb bcla...@globalcloud.net:
>
> Having the same issue as well. Any info would be greatly appreciated!
>
> Ben
>
> On Tuesday, February 5, 2013 5:40:53 AM UTC-5, DarkRift wrote:
>>
>> I'll
I'll setup da job that deletes selenium.log after each run till this issue
is fixed
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...
Having the same issue as well. Any info would be greatly appreciated!
Ben
On Tuesday, February 5, 2013 5:40:53 AM UTC-5, DarkRift wrote:
>
> I'll take a look into it,
>
> Richard
>
> On 2013-02-05, at 03:10, psiuk...@gmail.com wrote:
>
> Hello,
>
> from eclipse, my tests are running very well a
I'll take a look into it,
Richard
On 2013-02-05, at 03:10, psiuk.da...@gmail.com wrote:
> Hello,
>
> from eclipse, my tests are running very well and there are no problems at all.
>
> But if I run my tests from Jenkins, the selenium plugin increases the
> selenium.log for about 700mb each run
Hello,
from eclipse, my tests are running very well and there are no problems at
all.
But if I run my tests from Jenkins, the selenium plugin increases the
selenium.log for about 700mb each run.
It seems that there is any binary stuff appended to the log... look here:
"INFO: REQUEST : {platfo
