[
https://issues.apache.org/jira/browse/ARTEMIS-2953?focusedWorklogId=501082&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-501082
]
ASF GitHub Bot logged work on ARTEMIS-2953:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 15/Oct/20 12:24
Start Date: 15/Oct/20 12:24
Worklog Time Spent: 10m
Work Description: gtully commented on pull request #3305:
URL: https://github.com/apache/activemq-artemis/pull/3305#issuecomment-709277729
Adding dome debugging to the finalise, I am not finding any failures in the
integration tests but I see that lots of the unit tests leave pages dangling
that get cleaned up via finalize.
I will push a debug build to see what fails in the real broker tests.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 501082)
Time Spent: 20m (was: 10m)
> Page.finalize causing intermittent test failures
> ------------------------------------------------
>
> Key: ARTEMIS-2953
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2953
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.15.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.16.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I see two intermittent failures in the PR build jobs:
> * PageTest.testDamagedPage:115->testDamagedPage:230 » IllegalState Is closed
> Error:
> * PagingStoreImplTest.testConcurrentDepage:372->testConcurrentPaging:554 »
> IllegalState
>
> Both seem to result from concurrent calls to close via the Page.finalize
> finalize is hugely non deterministic, it should go. It may be that we need
> some more calls to close, lets see.
> note: both those tests use FakeSequentialFileFactory but I don't think the
> problem is in that.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
