On Thu, Apr 22, 2021 at 12:32 PM Lokesh Jain (Jira) <[email protected]> wrote:

> E
>     [
> https://issues.apache.org/jira/browse/HDDS-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327141#comment-17327141
> ]
>
> Lokesh Jain commented on HDDS-5099:
> -----------------------------------
>
> Sure [~arp], will review once PR is out.
>
> > Error with unit test for hdds.container-service
> TestSchemaOneBackwardsCompatibility
> >
> -----------------------------------------------------------------------------------
> >
> >                 Key: HDDS-5099
> >                 URL: https://issues.apache.org/jira/browse/HDDS-5099
> >             Project: Apache Ozone
> >          Issue Type: Bug
> >            Reporter: Neil Joshi
> >            Assignee: Neil Joshi
> >            Priority: Minor
> >         Attachments: intermittent_err.png, intermittent_fix1.png
> >
> >
> > The unit test _testDelete_ from _TestSchemaOneBackwardsCompatibility_
> (_hadoop-hdds/container-service_) has an observed reproducible intermittent
> error.  This error is due to the test launching a background task
> (_BackgroundService.java_) that it expects to block to completion, however
> it does not.  The test, through a thread pool executor launches a task to
> delete blocks and expects to block until completion.   After blocked until
> completion it checks the worker result.  Since the current implementation
> does not block, at times the worker is not done before the test checks the
> condition, hence the intermittent error.
> >
> > Observed error:
> > {code:java}
> > mvn -Dtest=TestSchemaOneBackwardsCompatibility test{code}
> > (see attachment err)
> >
> >  With waiting until worker task is finished before checking condition:
> (see attachment showing test passed)
> >
> >
> >
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.4#803005)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to