[ 
https://issues.apache.org/jira/browse/SOLR-18001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated SOLR-18001:
----------------------------------
    Labels: pull-request-available  (was: )

> Flaky test failure - LBHttp2SolrClientIntegrationTest(testSimple) failing 
> because of  java.util.concurrent.TimeoutException
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-18001
>                 URL: https://issues.apache.org/jira/browse/SOLR-18001
>             Project: Solr
>          Issue Type: Test
>            Reporter: nikhilesh
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> While reviewing the recent [[PR| 
> [https://github.com/apache/solr/actions/runs/19502819074?pr=3880]]] - Noticed 
> a test failure with the stack trace as below. 
>  
> {code:java}
> LBHttp2SolrClientIntegrationTest > testSimple FAILED 
>  java.util.concurrent.TimeoutException 
>  at __randomizedtesting.SeedInfo.seed([FF03BA02B90FC185:C7B09EFC9EFC1554]:0) 
>  at 
> java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1960)
>  
>  at 
> java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2095)
>  
>  at org.eclipse.jetty.server.Server.doStop(Server.java:663) 
>  at 
> org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:132)
>  
>  at org.apache.solr.embedded.JettySolrRunner.stop(JettySolrRunner.java:630) 
>  at
>  {code}
> This test will run successfully locally and seems to be failing based on the 
> timeout exception which is tied to intermittent jetty shutdown taking longer.
> I am working on creating a fix for the same.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to