[
https://issues.apache.org/jira/browse/SOLR-10053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15847203#comment-15847203
]
Mark Miller commented on SOLR-10053:
------------------------------------
One of those fails looks like a RAM resource issue.
The more interesting one is:
{noformat}
[junit4] FAILURE 0.20s |
TestSolrCloudWithDelegationTokens.testDelegationTokenCancelFail <<<
[junit4] > Throwable #1: java.lang.AssertionError: expected:<200> but
was:<404>
{noformat}
> TestSolrCloudWithDelegationTokens failures
> ------------------------------------------
>
> Key: SOLR-10053
> URL: https://issues.apache.org/jira/browse/SOLR-10053
> Project: Solr
> Issue Type: Test
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Ishan Chattopadhyaya
> Attachments: fail.log, stdout, stdout
>
>
> The TestSolrCloudWithDelegationTokens tests fail often at Jenkins. I have
> been so far unable to reproduce them using the failing seeds. However,
> beasting these tests seem to cause failures (once after about 10-12 runs).
> Latest Jenkins failure:
> https://builds.apache.org/job/Lucene-Solr-NightlyTests-6.4/12/
> It wasn't apparent what caused these failures. To cut down the noise on
> Jenkins, I propose that we disable the test with @AwaitsFix (or bad apple)
> annotation and continue to debug and fix this test.
> WDYT, [[email protected]]?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
