Martijn, I guess you didn't see the commit and you assumed that I used : Random.nextInt() to get port number.
On Mon, Aug 5, 2013 at 9:39 AM, Martin Grigorov <[email protected]>wrote: > Why do you think so ? > By using "new Server(0)" Jetty will bind to a random and *unused* port. > > > > On Mon, Aug 5, 2013 at 9:32 AM, Martijn Dashorst < > [email protected]> wrote: > >> Which will fail randomly :-) >> >> though less frequently >> >> Martijn >> >> On Sat, Aug 3, 2013 at 9:30 AM, Sven Meier <[email protected]> wrote: >> > With Martin's last commit the HttpUnit based tests use a random port. >> > >> > Sven >> > >> > >> > On 08/03/2013 12:45 AM, Jeremy Thomerson wrote: >> >> >> >> Should we do something to avoid that? Could the different branches use >> >> different ports? Or some buildbot-config? >> >> >> >> >> >> On Fri, Aug 2, 2013 at 7:58 AM, Martin Grigorov >> >> <[email protected]>wrote: >> >> >> >>> You should commit with some delay between master and wicket-6.x >> because >> >>> otherwise wicket-examples' test fail to use the same http port... >> >>> >> >>> >> >>> On Fri, Aug 2, 2013 at 1:55 PM, <[email protected]> wrote: >> >>> >> >>>> The Buildbot has detected a new failure on builder wicket-branch-6.x >> >>> >> >>> while >> >>>> >> >>>> building wicket. >> >>>> Full details are available at: >> >>>> http://ci.apache.org/builders/wicket-branch-6.x/builds/103 >> >>>> >> >>>> Buildbot URL: http://ci.apache.org/ >> >>>> >> >>>> Buildslave for this Build: hemera_ubuntu >> >>>> >> >>>> Build Reason: scheduler >> >>>> Build Source Stamp: [branch wicket-6.x] >> >>>> cdfa92ca3f8af8012a8f5c53076c1ffb7ce65944 >> >>>> Blamelist: svenmeier <[email protected]> >> >>>> >> >>>> BUILD FAILED: failed compile >> >>>> >> >>>> sincerely, >> >>>> -The Buildbot >> >>>> >> >>>> >> >>>> >> >>>> >> >> >> >> >> > >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> > >
