[
https://issues.apache.org/jira/browse/SOLR-16584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648293#comment-17648293
]
ASF subversion and git services commented on SOLR-16584:
--------------------------------------------------------
Commit 7fe2a5a39103852e5f1c21ca3b99a2c8cb43bc12 in solr's branch
refs/heads/branch_9x from Kevin Risden
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=7fe2a5a3910 ]
SOLR-16584: BATS test fails stopping two instances (#1240)
* Assert that Solr has started before shutting back down again
* capture logs on test failure
Co-authored-by: Jan Høydahl <[email protected]>
> integrationTests (BATS) fail on GitHub and Jenkins
> --------------------------------------------------
>
> Key: SOLR-16584
> URL: https://issues.apache.org/jira/browse/SOLR-16584
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Integration Tests
> Affects Versions: main (10.0)
> Reporter: Jan Høydahl
> Assignee: Kevin Risden
> Priority: Major
> Time Spent: 6h 50m
> Remaining Estimate: 0h
>
> I discovered during my work on SOLR-16475
> ([PR|https://github.com/apache/solr/pull/1089]) that BATS tests run by
> {{./gradlew integrationTests}} failed consistently in GitHub, even if they
> always pass locally on my mac.
> [~krisden] followed up with [https://github.com/apache/solr/pull/1223] on
> main since my initial PR included some changes to BATS itself. It also failed
> on main.
> Relizing we do not run nightly integrationTest in Jenkins, I added
> {{integrationTests}} task to the regular
> [Solr-Check-Main|https://builds.apache.org/job/Solr/job/Solr-Check-main/]
> Jenkins job, and it now fails the same way as GitHub action does, except for
> [one run|https://builds.apache.org/job/Solr/job/Solr-Check-main/5544/] that
> passed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]