Re: Hi I'm Raphael

Hi Raphael, Welcome and thanks for taking an interest in helping out! Shawn's pointers above are all good for getting started. If there's any other information you need, let us know. You know best what you want to get involved with. But if you're interested in QA and are interested in the

Re: [lucene-solr] branch branch_8x_tmp created (now f4eea9b)

Thanks for catching this, Hoss. This is absolutely unacceptable. It shouldn't have been there. I just deleted it. Noble, please be careful about such mishaps. You could've named it "jira/_branch8x" or something. Please don't create any branch that doesn't start with "jira/" (unless you're the

Re: Hi I'm Raphael

On 2019/11/08 05:42:01, Shawn Heisey wrote: > On 11/7/2019 6:14 PM, Raphael Bircher wrote: > > Wich source tree I should build for testing purpose? I heard rumors, that > > installing Lucene is a bit rocket science. > > I'm here for Solr, and my interest in Lucene is only incidental,

Re: [lucene-solr] branch branch_8x_tmp created (now f4eea9b)

: Subject: [lucene-solr] branch branch_8x_tmp created (now f4eea9b) WTF is this branch_8x_tmp !?!?!?!??? Since when is this ok? -Hoss http://www.lucidworks.com/ - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For

Tracking down inconsistent failure in jenkins

Hi all In my welcome thread, Jason pointed me to Hoss's Jenkins failure page. I think this is a good point to start for me. I like to help you tracking down this inconsistent failures. At first, please, if I got something wrong, correct me! As far as I understand, there are tests in Jenkins

Re: Gradle build

+1 to option 2 On Thu, Nov 7, 2019 at 6:23 PM David Smiley wrote: > > Doing 2 doesn’t stop us going to 3 soon if we want. Easier to fix/improve > on one branch while it’s new. > > On Thu, Nov 7, 2019 at 5:41 PM Adrien Grand wrote: > >> I'd be fine with option 2 but I have a slight preference

Re: Tracking down inconsistent failure in jenkins

Hi all On 2019/11/08 23:56:00, Raphael Bircher wrote: > I was building solr and running the JUnit Tests now. The tests was running, but I don't find the testlogs ;-) I got two errors with a self builded solr from the head. I've also seen a Ubuntu machine on Jenkins with two errors. I let

Re: Tracking down inconsistent failure in jenkins

Raphael: Thanks for becoming involved! It’s super-frustrating that some of the tests on Jenkins do (or do not) reproduce, even if you “beast” them. Hoss’ reports come from many different environments, from Windows to various Java releases to… So “does it fail locally” is a tricky question.

Re: Tracking down inconsistent failure in jenkins

Hi Erick On 2019/11/08 22:49:31, Erick Erickson wrote: > Raphael: > > Thanks for becoming involved! > > It’s super-frustrating that some of the tests on Jenkins do (or do not) > reproduce, even if you “beast” them. Hoss’ reports come from many different > environments, from Windows to

Re: ReleaseWizard tool

Hi, Looking forward to feedback on the tool Ishan! One concrete question: I see that v8.2.0 is still in the release repo http://www.apache.org/dist/lucene/solr/ The Wizard step "9.10. Stop mirroring old releases" should have told you to remove v8.2.0

Re: Solr 8.3 Solrj streaming expressions do not return all field values

Before moving to a jira let's take a look at the underlying Solr queries in the log. The Streaming Expressions just creates solr queries, in this case queries to the /export handler. So when something is not working as expected we want to strip away the streaming expression and debug the actual