What you're trying to do is entirely possible. One issue may be that
your remote machines aren't submitting to the right URL. Can you try
to see whether those machines are submitting to the right place (e.g.
http://remotehost:8080/...)? If not, then most likely, the URL you're
giving to the remote machines doesn't include the
"submitResults=<url>" parameter. "submitResults=true" means "submit
the results to the standard localhost URL".
"submitResults=http://remotehost:8080/..." means submit results to
that URL. Are you passing in the right submitResults value?

- Edward

--- In jsunit@yahoogroups.com, "alexvollmer" <alex.vollmer@g...> wrote:
> I've been playing with JSUnit to see if I can deploy a single server
> with all of my JSUnit tests and code. I want to deploy several other
> servers (with the various OS/browser combos) that are configured to
> point back to my main test server. Then I would like to run the
> 'distributed_test' task from the main server with the
> 'remoteMachineURLs' set to the various OS/browser servers I setup
> earlier.
>
> I can only get this to work if I configure each os/browser server to
> use local files (for the testRunner and the test page), but when I
> configure it to use my main server it times out sending the results.
> For example on a linux box I get a message like this before the test
> fails:
> [java] Wed Sep 22 11:42:12 PDT 2004: StandaloneTest: waiting for
> /usr/bin/firefox to submit result
> [java] F
> [java] Time: 121.261
> [java] There was 1 failure:
>
>
> I don't want to deploy my test code on each os/browser server because
> I'm trying to get the whole thing to be part of an automated build
> (cruisecontrol) where the source code is updated from version control
> and deployed in a single place.
>
> Any help or insight into the problem would be greatly appreciated.
>
> Thanks!
>
> --Alex Vollmer