Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SOLR-16784 Frequent failing CollectionReloadTest #1662

Merged
merged 2 commits into from
May 25, 2023

Conversation

stillalex
Copy link
Member

@stillalex stillalex commented May 24, 2023

https://issues.apache.org/jira/browse/SOLR-16784

Description

Test was failing with 404 due to incorrect api calls every time the random picker chose '2'. I updated the urls and payload to the correct version and now it works.
I'm also taking the opportunity to fix one minor accidental change in TestPullReplica test class.

Solution

Please provide a short description of the approach taken to implement your solution.

Tests

Please describe the tests you've developed or run to confirm this patch implements the feature or solves the problem.

Checklist

Please review the following and check all that apply:

  • I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
  • I have created a Jira issue and added the issue ID to my pull request title.
  • I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
  • I have developed this patch against the main branch.
  • I have run ./gradlew check.
  • I have added tests for my changes.
  • I have added documentation for the Reference Guide

@dsmiley
Copy link
Contributor

dsmiley commented May 24, 2023

@gerlowskija just checking / reminding myself -- these big changes in V2 API are not expected to be backwards-compatible; right?

Copy link
Contributor

@epugh epugh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks @stillalex for fixing the test that I helped bring in, and then we had to BadApple it! I felt bad about it ;-)

@gerlowskija
Copy link
Contributor

Yep, @dsmiley ! The v2 API is "experimental" so that we can change it without deference to backcompat. Of course, if a PR meant to update a v2 API breaks the corresponding v1, that'd still be an issue/violation. But breaking changes to v2 are "expected".

@@ -128,7 +128,7 @@ public void tearDown() throws Exception {
@Repeat(iterations = 30)
public void testCreateDelete() throws Exception {
try {
switch (2 /*random().nextInt(3)*/) {
switch (random().nextInt(3)) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[+1] This line by Alex fixes a mistake I made here. I commented it out while testing a PR a week or two back, and it accidentally got added to my PR and merged.

Good catch Alex!

@epugh epugh merged commit f6de836 into apache:main May 25, 2023
2 checks passed
@epugh
Copy link
Contributor

epugh commented May 25, 2023

Thank you @stillalex for this!

epugh pushed a commit that referenced this pull request May 25, 2023
* SOLR-16784 Frequent failing CollectionReloadTest

* enabling random selection in TestPullReplica
@stillalex
Copy link
Member Author

thanks @epugh for merging!

@stillalex stillalex deleted the SOLR-16784 branch May 25, 2023 17:29
epugh pushed a commit that referenced this pull request Jun 21, 2023
* SOLR-16784 Frequent failing CollectionReloadTest

* enabling random selection in TestPullReplica
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants