HoustonPutman commented on PR #2230:
URL: https://github.com/apache/solr/pull/2230#issuecomment-2448411374
@noblepaul this doesn't actually make the collection PRS, instead it just
creates the collection in a PRS-way. I will make a PR that shows the tests that
break when PRS collections are
HoustonPutman commented on PR #2230:
URL: https://github.com/apache/solr/pull/2230#issuecomment-2091267170
Fair enough. We will let it bake then backport both.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL ab
dsmiley commented on PR #2230:
URL: https://github.com/apache/solr/pull/2230#issuecomment-2091201004
The approach seen here is perfect -- bake something risky in main _then_
bring to branch_9x.
--
This is an automated message from the Apache Git Service.
To respond to the message, please
HoustonPutman commented on PR #2230:
URL: https://github.com/apache/solr/pull/2230#issuecomment-2091147056
Why isn't any of this PRS testing logic backported to 9x @noblepaul ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub a
HoustonPutman commented on PR #2230:
URL: https://github.com/apache/solr/pull/2230#issuecomment-2088918365
Ok created a PR to fix this, I'm not sure what the logic here was supposed
to be, but I've changed PRS to be a much more normal per-test-class randomized
option.
--
This is an autom
gus-asf commented on PR #2230:
URL: https://github.com/apache/solr/pull/2230#issuecomment-2088385840
Neither this PR nor the commit mention a jira so I'll drop this here:
https://issues.apache.org/jira/browse/SOLR-17265
--
This is an automated message from the Apache Git Service.
To respo
gerlowskija commented on PR #2230:
URL: https://github.com/apache/solr/pull/2230#issuecomment-2088376107
+1 I spent a bunch of time on this this morning after running into
OverseerStatusTest failures on main, before stumbling on this discussion. Any
chance you're able to investigate furthe
dsmiley commented on PR #2230:
URL: https://github.com/apache/solr/pull/2230#issuecomment-2070113298
@noblepaul OverseerStatusTest still fails occasionally :-( A number of
people have bumped into it and maybe wasted some time trying to figure out what
happened. Something has to be done.
dsmiley commented on PR #2230:
URL: https://github.com/apache/solr/pull/2230#issuecomment-2001627945
And LocalFSCloudIncrementalBackupTest
https://ge.apache.org/scans/tests?search.relativeStartTime=P90D&search.rootProjectNames=solr-root&search.timeZoneId=America%2FNew_York&tests.container
dsmiley commented on PR #2230:
URL: https://github.com/apache/solr/pull/2230#issuecomment-2001603190
TestLocalFSCloudBackupRestore failures seems plausibly related as its
failures begin at the same time:
https://ge.apache.org/scans/tests?search.relativeStartTime=P90D&search.rootProjectNa
dsmiley commented on PR #2230:
URL: https://github.com/apache/solr/pull/2230#issuecomment-1984571357
BTW it's nice to see PRS used/tested more :-)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to
dsmiley commented on PR #2230:
URL: https://github.com/apache/solr/pull/2230#issuecomment-1984524318
I believe this has caused NullPointerExceptions in OverseerStatusTest --
createcollection is null. Quite a number of test failures for this since this
was merged.
--
This is an automated
noblepaul merged PR #2230:
URL: https://github.com/apache/solr/pull/2230
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.
13 matches
Mail list logo
