[
https://issues.apache.org/jira/browse/LUCENE-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless updated LUCENE-5937:
---------------------------------------
Attachment: LUCENE-5937.patch
Patch, that just sends the output to a temp file, and on failure streams it
back...
But one backside to this approach is ... it can alter the test's behavior since
the thread interrupts can now arrive while IW is printing to the infoStream,
change the timing of IW's operations, etc. ...
I wanted to do this originally because when this test fails, it's very hard to
repro, and the failure log can tell us details about what happened, but right
now some details are missing such as when MDW's virus checker kicked in to
prevent certain file deletions. Ideally we would also get MDW's confessions
into the log ... but that would mean setting an infoStream on MDW which is
scary to me.
> Can we fix TestIW.testThreadInterruptDeadlock to capture IW infoStream
> ----------------------------------------------------------------------
>
> Key: LUCENE-5937
> URL: https://issues.apache.org/jira/browse/LUCENE-5937
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/index
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 4.11, 5.0
>
> Attachments: LUCENE-5937.patch
>
>
> I already tried the "obvious" approach but this quickly OOMEs since IW just
> prints too much stuff ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
