I guess it wasn't mistake. Lots of our tests produces big exception
stacktraces and tests have very big logs. But maybe it won't be so bad
now as travis build is divided into multiple parts and the limit is
separate for each part? Maybe we can try to enable it and see how big
logs are and if travis is still ok?
But another thing I was thinking was to increase webDriver timeout to 1
hour when running from IDE. Currently it's 10 seconds. But I am
personally usually want to debug server or adapter when I am running
tests from IDE and I am continuously overriding the system property to
increase timeout. I suspect that people usually run test from IDE when
they develop new test or debug existing test, so having bigger timeout
makes sense?
Marek
On 13/07/17 07:07, Stian Thorgersen wrote:
I remember we talked about this, but not the details. I suspect it
was
disabled just by mistake. Jenkins primarily uses auth-server-wildfly
and this won't have any effect there as it'll all be controlled
through standalone.xml and use default logging there.
On 12 July 2017 at 17:14, Marek Posolda <mposolda(a)redhat.com
<mailto:mposolda@redhat.com>> wrote:
I guess that logging for keycloak server was disabled because of
big Travis and Jenkins logs? AFAIK it was always disabled in
testsuite-arquillian from day 1. Due to this, I was thinking that
enabling the logging in maven is just not an option, so I've added
this listener just to ensure that logging is enabled in IDE.
Marek
On 12/07/17 08:58, Stian Thorgersen wrote:
What's the point of this? I don't see why we would want to
disable Keycloak
server logging when running from Maven?
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org <mailto:keycloak-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/keycloak-dev
<
https://lists.jboss.org/mailman/listinfo/keycloak-dev>