JavaScript waitForPage() handler be added when rendering a partial Ajax response

2012-01-05 Thread gs_tapestry
Hi, I am upgrading to Tapestry5.2.6 and ran into an error which didn't occur with T5.0. My page template is like : http://tapestry.apache.org/schema/tapestry_5_1_0.xsd";> # advancedSearch

buildbot success in ASF Buildbot on tapestry-trunk

2012-01-05 Thread buildbot
The Buildbot has finished a build on builder tapestry-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tapestry-trunk/builds/21 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: isis_ubuntu Build Reason: scheduler Build Source Stamp:

buildbot success in ASF Buildbot on tapestry-trunk

2012-01-05 Thread buildbot
The Buildbot has finished a build on builder tapestry-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/tapestry-trunk/builds/22 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: isis_ubuntu Build Reason: scheduler Build Source Stamp:

Build failed in Jenkins: tapestry-trunk-freestyle #651

2012-01-05 Thread Apache Jenkins Server
See Changes: [hlship] Remove deprecated AbstractIntegrationTestSuite class, refactor tests that used it Remove deprecated JettyRunner [hlship] Remove deprecated AbstractIntegrationTestSuite class, refactor tests that used it

Failing build

2012-01-05 Thread Igor Drobiazko
The build is failing since December 15th. Apart from Ajax test that fail from time to time, we have a test case which fails constantly. See the following link. https://builds.apache.org/job/tapestry-trunk-freestyle/ws/trunk/tapestry-core/build/reports/tests/Tapestry%20Core/Service%20Unit%20Tests.h

Re: Failing build

2012-01-05 Thread Howard Lewis Ship
I wonder if this is a real bug caused by, perhaps, some different JDK configuration on the Jenkins server than on our workstations? On Thu, Jan 5, 2012 at 12:45 PM, Igor Drobiazko wrote: > The build is failing since December 15th. Apart from Ajax test that fail > from time to time, we have a test

Re: Failing build

2012-01-05 Thread Massimo Lusetti
On Thu, Jan 5, 2012 at 10:30 PM, Howard Lewis Ship wrote: > I wonder if this is a real bug caused by, perhaps, some different JDK > configuration on the Jenkins server than on our workstations? I don't know which configurations could cause that but indeed the test suite is running fine in both m

Re: Failing build

2012-01-05 Thread Josh Canfield
The test machine probably has a non-UTF8 character encoding. You can make this test fail locally if you set the -Dfile.encoding to something other than UTF-8 when you run the tests. In XMLTokenStream.openStream() adding explicit encoding fixes the problem InputStreamReader rawReader = ne