[
https://issues.apache.org/jira/browse/MYFACES-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689603#comment-17689603
]
Werner Punz edited comment on MYFACES-4564 at 2/16/23 8:34 AM:
---------------------------------------------------------------
Found it, the default implicitWait for finding elements is 0miliseconds...
Now we have a tad slower response code we run into a race condition. The fix
simply is to raise the implicit wait time!
was (Author: werpu):
The issue might be that all the elements are there but the content condition is
not yet met.
The implicit wait for finding an element is 6s!!! So we can rest assure it
waits until an element is found. The original log says wait 0s with an interval
of 500ms so it bombs out immediately of the trigger wait for condition code!
> Test failure in the table test on RC5 build
> -------------------------------------------
>
> Key: MYFACES-4564
> URL: https://issues.apache.org/jira/browse/MYFACES-4564
> Project: MyFaces Core
> Issue Type: Task
> Affects Versions: 4.0.0-RC5
> Reporter: Werner Punz
> Assignee: Werner Punz
> Priority: Major
>
> Report by [~volosied]
> [INFO] [ERROR] Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time
> elapsed: 21.554 s <<< FAILURE! - in
> org.apache.myfaces.core.integrationtests.ajax.IntegrationTest
> [INFO] [ERROR]
> org.apache.myfaces.core.integrationtests.ajax.IntegrationTest.testBasicTable
> Time elapsed: 6.733 s <<< ERROR!
> [INFO] org.openqa.selenium.TimeoutException: Expected condition failed:
> waiting for
> org.apache.myfaces.core.integrationtests.ajax.IntegrationTest$$Lambda$675/0x000000080085b040@2f54f746
> (tried for 0 second(s) with 500 milliseconds interval)
> [INFO] at
> org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:87)
> ...
> [INFO] at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:169)
> [INFO] at
> org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:595)
> [INFO] at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:581)
> [INFO] Caused by: org.openqa.selenium.NoSuchElementException: no such
> element: Unable to locate element: \{"method":"css
> selector","selector":"#head_row1_0"}
> [INFO] (Session info: headless chrome=110.0.5481.100)
> ...
> This is very likey a timeout issue, given the new ajax code is somewhat
> slower than the older one. The test needs to be fixed to wait for a dom
> condition with a higher timeout window. I will take over this!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
