This is an automated email from the ASF dual-hosted git repository.

benweidig pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tapestry-5.git


The following commit(s) were added to refs/heads/master by this push:
     new 72918c74c TAP5-2819: WebResourcesTest trying to fix timeout on Apache 
CI
72918c74c is described below

commit 72918c74c1c9ed4bd9c6aff0750188a193ba8235
Author: Ben Weidig <[email protected]>
AuthorDate: Sat Apr 18 13:40:50 2026 +0200

    TAP5-2819: WebResourcesTest trying to fix timeout on Apache CI
    
    The test_CoffeeScript_compilation test fails on Apache quite
    reproducable, but neither local or on my own CI server.
    
    My educated guess is that the inital Rhino initialization takes too long
    for some reason, so the we hit the timeout.
    Therefore, I set the Selenium timeout before the open call, but only in
    this test.
    It will also affect test_Less_compilation but this one succeeded before
    anyway.
---
 .../src/test/java/t5/webresources/services/web/WebResourcesTest.java | 5 +++++
 1 file changed, 5 insertions(+)

diff --git 
a/tapestry-webresources/src/test/java/t5/webresources/services/web/WebResourcesTest.java
 
b/tapestry-webresources/src/test/java/t5/webresources/services/web/WebResourcesTest.java
index c4b932c81..d4d5bb7f5 100644
--- 
a/tapestry-webresources/src/test/java/t5/webresources/services/web/WebResourcesTest.java
+++ 
b/tapestry-webresources/src/test/java/t5/webresources/services/web/WebResourcesTest.java
@@ -26,6 +26,11 @@ public class WebResourcesTest extends SeleniumTestCase {
     @Test
     public void test_CoffeeScript_compilation()
     {
+        // It appears that the initial CoffeeScriptCompiler/Rhino 
initialization might
+        // take too long on Apache CI, so we allow Selenium some more time to 
wait
+        // after initiating the request.
+        setTimeout("90000"); // 90s
+
         open("/");
         waitForInitializedPage();
         assertEquals(getText("banner"), "Index module loaded, bare!");

Reply via email to