[
https://issues.apache.org/jira/browse/METRON-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15826317#comment-15826317
]
ASF GitHub Bot commented on METRON-666:
---------------------------------------
Github user cestella commented on the issue:
https://github.com/apache/incubator-metron/pull/418
So, one comment here for posterity and to make sure we're all on the same
page. This error started happening yesterday to my PR (#417). Here's what
happened:
* @mmiklavc asked for a doc change to a `README.md`
* Upon that commit, the SolrIntegrationTest failed because it timed out.
* I ran it 5 times in succession locally and noted that the total time was
around the same as historically (32 - 35 minutes)
* Meanwhile, I updated the test to be a bit more permissive timeout-wise
for the IndexingIntegrationTests
I concluded that it was travis latency based on:
* It is sporadic on travis but not locally
* Performance regressions did not appear locally
* It appeared suddenly on #417 after a no-code-change commit.
Just pointing out when I noticed this and some context.
> Fix javadoc doclint errors
> --------------------------
>
> Key: METRON-666
> URL: https://issues.apache.org/jira/browse/METRON-666
> Project: Metron
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Matt Foley
> Assignee: Matt Foley
>
> Java 8 includes "doclint" as part of javadocs. As a result, running javadoc
> on current code base has fatal errors, mostly (not all) related to use of
> "<p/>" (not allowed ever), or unmatched "</p>" (not preceded by a matching
> "<p>"). It is, however, happy with unmatched "<p>", so that's the thing to
> use for paragraph separators. Put it on the same line as the next line of
> text to avoid a warning about "empty <p>".
> There are other errors fixed here too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
