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

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

> Intermittent failure in TestBlockDataStreamOutput.closeAfterWriteFailureThrows
> ------------------------------------------------------------------------------
>
>                 Key: HDDS-16482
>                 URL: https://issues.apache.org/jira/browse/HDDS-16482
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: test
>            Reporter: Attila Doroszlai
>            Assignee: Andy Huang
>            Priority: Major
>              Labels: pull-request-available
>
> After HDDS-16084 
> [fixes|https://github.com/apache/ozone/pull/11056/files#diff-159766d1c2c1c9f2376a001e946ae34694779c2abf213affa6677d2c8f8263e9R222]
>  a no-op assertion, TestBlockDataStreamOutput becomes flaky:
> {code:title=https://github.com/apache/ozone/actions/runs/35043021459/job/104629862556?pr=11056#step:13:1744}
> [ERROR] Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
> 1.911 s <<< FAILURE! -- in 
> org.apache.hadoop.hdds.scm.storage.TestBlockDataStreamOutput
> [ERROR] 
> org.apache.hadoop.hdds.scm.storage.TestBlockDataStreamOutput.closeAfterWriteFailureThrows
>  -- Time elapsed: 0.015 s <<< FAILURE!
> java.lang.AssertionError: 
> Expecting actual:
>   "Unexpected Storage Container Exception: 
> java.util.concurrent.CompletionException: Failed to write chunk 1_chunk_2 
> into block conID: 1 locID: 1 bcsId: 0 replicaIndex: null"
> to contain:
>   "chunk write failed due to injected failure" 
>       at 
> org.apache.hadoop.hdds.scm.storage.TestBlockDataStreamOutput.closeAfterWriteFailureThrows(TestBlockDataStreamOutput.java:222)
> {code}



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