I couldn't hold back investigating a bit more.
Like described in my last post, the timeout always occurred/started
in a GWTTestCase class that contained two test cases that involve RPC
calls.
I did split up these test cases such that they have their own
GWTTestCase class, and the timeout
On Wed, Oct 20, 2010 at 9:22 AM, Ed post2edb...@gmail.com wrote:
I couldn't hold back investigating a bit more.
Like described in my last post, the timeout always occurred/started
in a GWTTestCase class that contained two test cases that involve RPC
calls.
I did split up these test cases
I give up for now :(...
This issue is getting me against the roof... :(
Even with remote debugging it all go well
But let's not forget that the error only occurs sometimes: about 50%
of the time and mostly during the day when I run the build manually
when the server is more busy. During the night
Yesterday my test was run with success and last night it failed again,
without anything changing in the meantime :(
I was digging a bit more in the GWT Junit test code and I think the
test fails because I don't use a servlet that is hosted by the Tomcat
container started by GWT.
Like Freeland
Hi John,
Thanks for your reply.
There are really two apps running in this case. First, there is the one
created by JUnitShell, which contacts an RPC servlet to manage running the
test. The timeout you see is because that servlet didn't get contacted.
Could you please give me some more info
On Tue, Oct 5, 2010 at 8:47 AM, Ed post2edb...@gmail.com wrote:
There are really two apps running in this case. First, there is the one
created by JUnitShell, which contacts an RPC servlet to manage running
the
test. The timeout you see is because that servlet didn't get contacted.
On Oct 5, 2:51 pm, John Tamplin j...@google.com wrote:
I also use Selenium, have about 2500 tests that run through Selenium,
that take about 50 hours to complete ;)...
Some background info:
I don't use runstyle for this. I run the tests against production
ready code produced during the
Thanks,
I found the servlet you meant: JUnitHostImpl
I see that the url that touches this servlet is correctly forwarded by
the proxy and received by this servlet when debugging in Eclipse:
The url that touches it: /
com.bv.gwt.profile.intern.ProfileGwtTest.JUnit/junithost (also appears
in the
On Tue, Oct 5, 2010 at 10:12 AM, Ed post2edb...@gmail.com wrote:
I found the servlet you meant: JUnitHostImpl
I see that the url that touches this servlet is correctly forwarded by
the proxy and received by this servlet when debugging in Eclipse:
The url that touches it: /
running the test in your continuous build environment with remote debugging
enabled and attaching to it with a debugger to see what is going on.
Thanks again. John
I did that already but will do it again now that I have a better
understanding of the GWT Junit code.
(I only have to use some
Today the nightly build failed again and no compiler error occurred as
appears in the above log snippet :(
Below the concerning logging snippet.
In the logging you see that the Proxy servlet does forward calls to
the parent class: GWT servlet: GWTShellServlet (No Proxy forward in
the logging means
Just played with the -runStyle Manual option
I am afraid that is not a correct option for me as I will run the
tests during the nightly build and with -runStyle option Manual will
stop when running the test and I have to manually copy/past the
displayed url, like explained in:
Thanks for the details, it gives me a better understanding of what's
going on such that I know where to look.
I notices that issue 4700 (the compiler errors) isn't of concern
during the nightly build as during the build all sources are correctly
included through the GWT maven plugin (not compiler
Thanks for the detailed explanation, that sure helps.
I have seen the timeout message happen due to a compile error in the GWT
code, but you'd see those errors in the log also.
Could it have something to do with issue 4700 ?:
http://code.google.com/p/google-web-toolkit/issues/detail?id=4700
On Fri, Oct 1, 2010 at 12:32 PM, Ed post2edb...@gmail.com wrote:
Thanks for the detailed explanation, that sure helps.
I have seen the timeout message happen due to a compile error in the GWT
code, but you'd see those errors in the log also.
Could it have something to do with issue 4700 ?:
15 matches
Mail list logo
