[
https://issues.apache.org/jira/browse/SOLR-5488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868758#comment-13868758
]
Erick Erickson commented on SOLR-5488:
--------------------------------------
[[email protected]] [~sbower]
How should we proceed? We're really back to debugging by println, shades of my
youth.
Mark:
What's your linux setup? A VM or bare metal? I can't seem to get this to happen
locally, although I'll give it a concentrated effort today on my Mac. Otherwise
I could install a VM I suppose.... Or would you be willing to apply some
debug-only patches and run?
Steve:
In order to track this down, and since it's on trunk, what do you think about
providing some debug patches (let's call them something like
SOLR-5488-debug.patch). If nobody objects we can put them on trunk and let
Jenkins reproduce the problems and examine the tracing. Maybe this would just
be changing the log level...
Of course if I can get this to happen locally I can run things, but I haven't
seen this locally yet.
Let me know...
> Fix up test failures for Analytics Component
> --------------------------------------------
>
> Key: SOLR-5488
> URL: https://issues.apache.org/jira/browse/SOLR-5488
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.0, 4.7
> Reporter: Erick Erickson
> Assignee: Erick Erickson
> Attachments: SOLR-5488.patch, SOLR-5488.patch, SOLR-5488.patch
>
>
> The analytics component has a few test failures, perhaps
> environment-dependent. This is just to collect the test fixes in one place
> for convenience when we merge back into 4.x
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
