#Freebsd mucommander update
#Freebsd mucommander software
#Freebsd mucommander windows

It took us two hours and a hint from Yonik to find the issue behind this ( SOLR-2673): But when starting to test the Solr builds, the problems began again: Some tests sometimes failed with strange error messages, but only randomly. The Lucene builds then passed fine most of the time, but we had some additional failures in another test inside the new facetting module: LUCENE-3346 (see below). On Sunday morning I gave Jenkins another chance: To proceed with testing on Jenkins, I hacked the shell scripts again to pass the following args to the Lucene test suite (only for Java 7 builds): -Dargs='-XX:CompileCommand=exclude,org/apache/lucene/analysis/en/PorterStemmer,ends' The rest of the day we also fixed another small issues in our test cases (TestWordDelimiterFilter failed because it used a character that changed properties in Java 7 - Robert committed a fix for this). Robert opened a bug report at Oracles bug tracker: #7070134 Step for step, he disabled compilation of several porter stemmer methods until he reached PorterStemmer.ends(). I stopped the 2-hourly builds with Java 7 on the Jenkins slave, as we did not want to spam the mailing list with failed build reports. Robert opened LUCENE-3335 and started to investigate the problem. That clearly shows, there was an hotspot optimization bug, as they are only triggered when a method is executed ten thousand times. Important was that the issue only appeared when I raised the number of test iterations, with the default of 1, the test passed.

#Freebsd mucommander windows

I started the analyzer tests locally on my windows box, bumm - same issue. but a few weeks ago a user on the Solr mailing list reported a crash in PorterStemmer, too' (see this post). We were shocked, 'this is just a stupid FreeBSD problem, I am sure. As I was only running the core tests on my local machine, this was not yet discoverered. live.ĭuring the tests of the new analyzers module suddenly we got a crash with SIGSEGV in TestPorterStemmer. Robert and me were watching the build output. I cloned the Jenkins jobs for the half-hourly test builds (3.x and trunk), hacked the shell scripts a little bit and started the first build. After approx 25 minutes, the build was done and the package installed. In parallel I also rebuilt the openjdk6 package for the standard test runs (a fix for a IPv6 bug was already available, so we were able to use latest version).

#Freebsd mucommander update

I logged onto the jenkins slave machine and started to update ports and built the openjdk7 package. I already installed the 64bit Windows preview build from Oracle (b147) on my Thinkpad and checked out the Lucene Core tests, which ran fine.Ī quick review showed that OpenJDK7 build 147 was already available in the FreeBSD ports collection. Our first problem was that the Jenkins server of Lucene runs under FreeBSD, so the chances were high, that we get no recent release of OpenJDK 7 running. 'Maybe we should add some Jenkins jobs to the Apache build server to test Apache Lucene/Solr trunk and 3.x branches?' As always, Robert and me had some quick Google Talk session and I pointed out my plans. I noticed that there is only one week left until Oracle plans to release Java 7. One news article stepped into my eye: ' Gearing up for Java 7' (english version). I checked my Lucene JIRA issues and after I helped my GSoC student, I read Heise newsticker. Last Saturday I woke up in the morning and had no real plans for the weekend. I want to start with a chronological summary about what happened since last weekend:

#Freebsd mucommander software

Some guys already blamed the Apache Software Foundation because they may have used the hype around Java 7 to fight against Oracle (since they stepped out of JCP). Since Oracle's release of Java 7 on Thursday last week, a lot of myths around the problem with Porter stemmer, wrong calculations in pulsing codec, and corrupt indexes appeared on the web. I started this blog about two months ago, but until now, I had no time to write any posts.