Shash:
> Looks like the build-tests.sh script works just fine under Cygwin/Bash
> on Win-XP.
Great!
> Also, I've just opted in for compile-farm access at SF, we should be
> able to setup nightly builds for Mac, Solaris, and some other Linux
> variants shortly.
Excellent Idea - I'd forgotten that was possible.
> I just turned on installs for Anteater and Axis to true in
> ant.properties, since those are required now.
>
> I am having trouble with functional tests on the default deploy. If I
> run from the script, the reports/default/anteater directory doesn't get
> created (I've attached the log file). Looks like the app-crud login is
> timing out because Tomcat is taking long to startup on my poor 500MHz
> PC, and anteater is timing out. Where can I increae that timeout?
That's in build-tests.sh, there's a "sleep" while tomcat fires up - or if you mean the
webapp itself is taking too long, I think you can add a delay in the anteater script,
but I don't immediately recall how....
> If I run tomcat, wait, and then run "ant anteater" directly in
> keel-build, then the directory gets created, but the app-crud test is
> failing....because (an excerpt):
>
> Expected to match pattern: .*Logged in as.* Got: ' <html lang="en">
> <head> <meta http-equiv="content-type"
> content="text/html;charset=iso-8859-1"> <meta
> http-equiv="Content-Style-Type" content="text/css"> <link
> rel="stylesheet" href="/struts/navigate/menu.css" id="css_menu"> <style>
> a { color: #003366; } ul { margin-top: 1px; margin-bottom: 10px;} td {
> font-family: Tahoma, Verdana, sans-serif; font-size: 12px; } form {
> margin: 5px; } hr { color: #eeeeee; height : 1px; } .ctrl {font-family:
> Tahoma, Verdana, sans-serif; font-size: 12px
>
> Any ideas?
Looks like the previous test (the login) isn't logging in properly, or retaining the
login, as that test above should have it already logged in, if I recall. Nothing in
the log that gives a hint? Maybe the rest of the error output will have a message or
trace - this looks like the output of the JavaScript menu, which goes on for a *long*
while in the page :-). Are we calling verify-login-seq here? It should be just
verify-login I think...
Mike
JGlobal Ltd.
http://www.jglobal.com
http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
