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

ASF GitHub Bot updated HDDS-11359:
----------------------------------
    Labels: pull-request-available  (was: )

> Intermittent timeout in TestPipelineManagerMXBean#testPipelineInfo
> ------------------------------------------------------------------
>
>                 Key: HDDS-11359
>                 URL: https://issues.apache.org/jira/browse/HDDS-11359
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Ethan Rose
>            Assignee: Chung En Lee
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: it-hdds.zip
>
>
> Seen in [this run|https://github.com/errose28/ozone/actions/runs/10511037945]
> {code}
> -------------------------------------------------------------------------------
> Test set: org.apache.hadoop.hdds.scm.pipeline.TestPipelineManagerMXBean
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 25.984 s <<< 
> FAILURE! - in org.apache.hadoop.hdds.scm.pipeline.TestPipelineManagerMXBean
> org.apache.hadoop.hdds.scm.pipeline.TestPipelineManagerMXBean.testPipelineInfo
>   Time elapsed: 25.927 s  <<< ERROR!
> java.util.concurrent.TimeoutException: 
> Timed out waiting for condition. Thread diagnostics:
> Timestamp: 2024-08-22 04:26:47,454
> {code}
> This previously showed up as an assertion failure until HDDS-9537 introduced 
> a wait for the condition. It seems the condition is still sometimes not 
> satisfied, but the error now shows up as a timeout.



--
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