> Switching to gradle means deleting tons of crap - all sorts of work arounds
> and ant abuse go away.
True. But other things will creep in. Take a look at any larger gradle
build -- there's lots of groovy-code magic in there...
To be clear: I do think the switch over to gradle is worth it (for
[
https://issues.apache.org/jira/browse/LUCENE-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833542#comment-16833542
]
Tomoko Uchida commented on LUCENE-8793:
---
[~jun_o]: thanks for the nice patch!
I d
Build: https://builds.apache.org/job/Lucene-Solr-SmokeRelease-8.x/92/
No tests ran.
Build Log:
[...truncated 23880 lines...]
[asciidoctor:convert] asciidoctor: ERROR: about-this-guide.adoc: line 1:
invalid part, must have at least one section (e.g., chapter, appendix, etc.)
[asciidoctor:convert]
[
https://issues.apache.org/jira/browse/SOLR-13318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833539#comment-16833539
]
Munendra S N commented on SOLR-13318:
-
[~gerlowskija]
Thanks for merging this
In bra
I don't know that we need or want to do side by side, it's just doable. If
we did do that, certainly the goal would be to keep it short. Whatever
keeps people from pulling the rug out from under me if I work on this
further.
Any other bike-shedding to be done or major concerns?
This really will b
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-BadApples-8.x-Linux/54/
Java: 64bit/jdk-11.0.2 -XX:+UseCompressedOops -XX:+UseSerialGC
1 tests failed.
FAILED: org.apache.solr.cloud.TestCloudRecovery2.test
Error Message:
Timeout waiting to see state for collection=collection1
:DocCollection(
[
https://issues.apache.org/jira/browse/LUCENE-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomoko Uchida updated LUCENE-8793:
--
Attachment: Screenshot from 2019-05-06 13-45-40.png
> Enhanced UI for CustomAnalyzer : show an
[
https://issues.apache.org/jira/browse/LUCENE-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomoko Uchida updated LUCENE-8793:
--
Attachment: Screenshot from 2019-05-06 13-46-16.png
> Enhanced UI for CustomAnalyzer : show an
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-BadApples-master-Linux/201/
Java: 64bit/jdk-11.0.2 -XX:-UseCompressedOops -XX:+UseConcMarkSweepGC
All tests passed
Build Log:
[...truncated 2000 lines...]
[junit4] JVM J2: stderr was not empty, see:
/home/jenkins/workspace/Lucene-Solr-BadAppl
I agree that an easier-to-understand build is an important virtue we should
try to achieve here (for the reasons you mentioned). Our build is too
complex and non-standard. Any other benefits are icing on the cake.
RE "side by side"; that could weigh us down maintaining more; I hope this
isn't lo
[
https://issues.apache.org/jira/browse/SOLR-12562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833526#comment-16833526
]
David Smiley commented on SOLR-12562:
-
It's not clear how the field might not be in t
[
https://issues.apache.org/jira/browse/SOLR-13318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833520#comment-16833520
]
ASF subversion and git services commented on SOLR-13318:
Commit 5
[
https://issues.apache.org/jira/browse/SOLR-13318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833518#comment-16833518
]
ASF subversion and git services commented on SOLR-13318:
Commit 9
[
https://issues.apache.org/jira/browse/SOLR-13318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833516#comment-16833516
]
ASF subversion and git services commented on SOLR-13318:
Commit 4
[
https://issues.apache.org/jira/browse/SOLR-12562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833509#comment-16833509
]
Erick Erickson commented on SOLR-12562:
---
I can take the calls to *materialize()* ou
Error processing tokens: Error while parsing action
'Text/ZeroOrMore/FirstOf/Token/DelimitedToken/DelimitedToken_Action3' at input
position (line 79, pos 4):
)"}
^
java.lang.OutOfMemoryError: Java heap space
-
To unsubscribe
[
https://issues.apache.org/jira/browse/SOLR-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833508#comment-16833508
]
Noble Paul commented on SOLR-13320:
---
I've updated the patch to use `failOnVersionConfli
Build: https://builds.apache.org/job/Lucene-Solr-Maven-master/2556/
No tests ran.
Build Log:
[...truncated 18056 lines...]
BUILD FAILED
/x1/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-master/build.xml:673: The
following error occurred while executing this line:
/x1/jenkins/jenkins-slave/wo
Build: https://builds.apache.org/job/Lucene-Solr-BadApples-Tests-8.x/94/
1 tests failed.
FAILED:
org.apache.solr.security.AuditLoggerIntegrationTest.testQueuedTimeMetric
Error Message:
Expecting mean time on queue >10ms, got 1.0002
Stack Trace:
java.lang.AssertionError: Expecting m
[
https://issues.apache.org/jira/browse/SOLR-12562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833483#comment-16833483
]
Erick Erickson commented on SOLR-12562:
---
[~dsmiley] Thanks for the feedback. For al
[
https://issues.apache.org/jira/browse/LUCENE-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833481#comment-16833481
]
Jun Ohtani commented on LUCENE-8793:
!Screen Shot 2019-05-06 at 10.00.57.png|width=6
Gus:
I’d _really_ like this all to be in one place, so fire away. We’ve spent far
too much time working with clients and wondering “where the hell are the
timeouts for XYZ?”
IMO, they should _all_ be configurable in a single place, preferably sorl.xml.
If you’re ambitious, a few comments in so
[
https://issues.apache.org/jira/browse/LUCENE-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Ohtani updated LUCENE-8793:
---
Attachment: LUCENE-8793.patch
> Enhanced UI for CustomAnalyzer : show analysis steps
> -
[
https://issues.apache.org/jira/browse/LUCENE-8793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Ohtani updated LUCENE-8793:
---
Attachment: Screen Shot 2019-05-06 at 10.00.57.png
> Enhanced UI for CustomAnalyzer : show analysis
[
https://issues.apache.org/jira/browse/SOLR-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Noble Paul updated SOLR-13320:
--
Attachment: SOLR-13320.patch
> add a param ignoreVersionConflicts=true to updates to not overwrite exis
Jun Ohtani created LUCENE-8793:
--
Summary: Enhanced UI for CustomAnalyzer : show analysis steps
Key: LUCENE-8793
URL: https://issues.apache.org/jira/browse/LUCENE-8793
Project: Lucene - Core
Issu
We can indeed make them work side by side.
- Mark
On Sun, May 5, 2019 at 11:36 AM Erick Erickson
wrote:
> I don’t know enough about the differences to even think consider
> complaining.
>
> Is the proposal that we use Gradle for master and continue to use ant for
> 8x? As long as the two build
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.1-Linux/288/
Java: 64bit/jdk-12 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.cloud.HttpPartitionTest.test
Error Message:
Error from server at http://127.0.0.1:44185: Underlying core creation failed
wh
msokolov commented on issue #657: LUCENE-8781: FST direct arc addressing
URL: https://github.com/apache/lucene-solr/pull/657#issuecomment-489466752
Thanks Dawid; while adding the CHANGES entry, I realized that the patch was
not in fact enabling the new encoding for suggesters! Somehow I had
[
https://issues.apache.org/jira/browse/SOLR-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833464#comment-16833464
]
Noble Paul commented on SOLR-13320:
---
yeah, the name can be misleading. even {{continueO
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-master/1841/
All tests passed
Build Log:
[...truncated 63041 lines...]
-ecj-javadoc-lint-src:
[mkdir] Created dir: /tmp/ecj2133797719
[ecj-lint] Compiling 69 source files to /tmp/ecj2133797719
[ecj-lint] invalid Class-Path header
[
https://issues.apache.org/jira/browse/SOLR-13320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833460#comment-16833460
]
Yonik Seeley commented on SOLR-13320:
-
Hmmm, when I read "ignoreVersionConflicts" I a
I'm not particularly moved by any performance differences. And the gradle
daemon is not my friend.
I see the main benefits of gradle as:
Our current ant+ivy+maven system is an insanely complicated Frankenstein.
It's high barrier of entry for new devs and does our project a disservice.
Adding or c
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/24039/
Java: 64bit/jdk-13-ea+18 -XX:-UseCompressedOops -XX:+UseSerialGC
8 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.update.processor.DistributedUpdateProcessorTest
Error Message:
SOLR-11606: ByteBuddy used by
[
https://issues.apache.org/jira/browse/SOLR-12562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833438#comment-16833438
]
David Smiley commented on SOLR-12562:
-
Can you see if we can remove {{materialize()}}
Sure, maybe. My feelings towards Gradle range from love to fury (and
quite frequently in short time spans). For example I'm sort of
wondering what will happen to those build machines (which aren't
exactly speed beasts) when you launch multiple builds on different
JVMs; gradle is fast once it has an
@Martin, yeah I expected that to work initially, but it has no effect on
the streaming expression code path.
@Kevin, thx for the link :)
On Sun, May 5, 2019, 2:49 PM Martin Gainty wrote:
> both connectionTimeout and socketTimeout are declared in
> $SOLR_HOME/solr.xml
>
> class="HttpSha
[
https://issues.apache.org/jira/browse/SOLR-13263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833433#comment-16833433
]
David Smiley commented on SOLR-13263:
-
bq. SpatialHeatmapFacetsTest#testGeoJsonBounds
I think you're right on the tests part.
Task that are run by the QA Bot (
https://issues.apache.org/jira/browse/SOLR-13049?focusedCommentId=16832997&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16832997
) could benefit from caching though right?
On Sun, May 5, 201
both connectionTimeout and socketTimeout are declared in $SOLR_HOME/solr.xml
${socketTimeout:60}
${connTimeout:6}
From: Gus Heck
Sent: Sunday, May 5, 2019 1:35 PM
To: dev
Subject: Socket Timeouts
I'm working with a client that's trying to
I think most of the build time is spent in tests. Since we're using
randomization I don't think you'd gain much from caches?
Dawid
On Sun, May 5, 2019 at 8:24 PM Varun Thacker wrote:
>
> Over the last few months, I've realized the power of build caches.
>
> In the future could we have remote cac
You might be interested in:
https://issues.apache.org/jira/browse/SOLR-13389
Kevin Risden
On Sun, May 5, 2019 at 1:35 PM Gus Heck wrote:
> I'm working with a client that's trying to process a lot of data (billions
> of docs) via a streaming expression, and the initial query is (not
> surpris
[
https://issues.apache.org/jira/browse/SOLR-13420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833428#comment-16833428
]
Gus Heck commented on SOLR-13420:
-
Have I answered your concerns? I'd like to move this f
Over the last few months, I've realized the power of build caches.
In the future could we have remote caches for Jenkins? In which case the
Lucene/Solr QA bot will be significantly faster as well? And then it could
just run against all patches and even block commits that violate it?
On Sun, May 5
[
https://issues.apache.org/jira/browse/SOLR-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kesharee Nandan Vishwakarma updated SOLR-13410:
---
Attachment: SOLR-13410.patch
> Designated overseer not able to become
[
https://issues.apache.org/jira/browse/SOLR-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kesharee Nandan Vishwakarma updated SOLR-13410:
---
Attachment: (was: SOLR-13410.patch)
> Designated overseer not abl
[
https://issues.apache.org/jira/browse/SOLR-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kesharee Nandan Vishwakarma updated SOLR-13410:
---
Attachment: SOLR-13410.patch
> Designated overseer not able to become
[
https://issues.apache.org/jira/browse/SOLR-13410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833426#comment-16833426
]
Kesharee Nandan Vishwakarma commented on SOLR-13410:
Hi [~ichattopadh
I'm working with a client that's trying to process a lot of data (billions
of docs) via a streaming expression, and the initial query is (not
surprisingly) taking a long time. Lots of various types of timeouts have
been cropping up and I've found myself thinking I solved some only to
discover that
dweiss commented on issue #657: LUCENE-8781: FST direct arc addressing
URL: https://github.com/apache/lucene-solr/pull/657#issuecomment-489445325
It all looks good, Mike. There is one remaining thing -- to add a
changes.txt entry in Lucene (under "improvements" section, I think). Add
yours
I don’t know enough about the differences to even think consider complaining.
Is the proposal that we use Gradle for master and continue to use ant for 8x?
As long as the two build systems can exist side by side (i.e. we can build
master by executing some Gradle target and continue to build 8x w
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/24038/
Java: 64bit/jdk-11 -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC
1 tests failed.
FAILED: org.apache.solr.cloud.NestedShardedAtomicUpdateTest.test
Error Message:
Error from server at http://127.0.0.1:34287/collection1: non ok
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-8.x/91/
9 tests failed.
FAILED: org.apache.solr.cloud.RollingRestartTest.test
Error Message:
Timeout occurred while waiting response from server at: http://127.0.0.1:44734
Stack Trace:
org.apache.solr.client.solrj.SolrServerException
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.x-Linux/517/
Java: 64bit/jdk1.8.0_201 -XX:+UseCompressedOops -XX:+UseSerialGC
1 tests failed.
FAILED: org.apache.solr.cloud.NestedShardedAtomicUpdateTest.test
Error Message:
Error from server at http://127.0.0.1:42113/collection1: non ok statu
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-8.x-Linux/516/
Java: 64bit/jdk-13-ea+18 -XX:-UseCompressedOops -XX:+UseG1GC
8 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.update.processor.DistributedUpdateProcessorTest
Error Message:
SOLR-11606: ByteBuddy used by Mockito i
Build: https://builds.apache.org/job/Lucene-Solr-NightlyTests-8.1/26/
3 tests failed.
FAILED: org.apache.solr.cloud.OverseerRolesTest.testDesignatedOverseerRestarts
Error Message:
Timed out waiting for overseer state change. The current overseer is:
127.0.0.1:37891_solr
Stack Trace:
java.lang.
Build: https://builds.apache.org/job/Lucene-Solr-BadApples-Tests-master/353/
1 tests failed.
FAILED: org.apache.solr.cloud.ReindexCollectionTest.testBasicReindexing
Error Message:
num docs expected:<200> but was:<199>
Stack Trace:
java.lang.AssertionError: num docs expected:<200> but was:<199>
[
https://issues.apache.org/jira/browse/LUCENE-8791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16833258#comment-16833258
]
Elbek Kamoliddinov commented on LUCENE-8791:
[~atris]
Hi Atri, Thanks for t
Build: https://jenkins.thetaphi.de/job/Lucene-Solr-master-Linux/24036/
Java: 64bit/jdk-13-ea+shipilev-fastdebug -XX:+UseCompressedOops -XX:+UseG1GC
12 tests failed.
FAILED:
junit.framework.TestSuite.org.apache.solr.update.processor.DistributedUpdateProcessorTest
Error Message:
SOLR-11606: ByteB
[
https://issues.apache.org/jira/browse/LUCENE-8791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elbek Kamoliddinov updated LUCENE-8791:
---
Attachment: LUCENE-8791.patch
> Add CollectorRescorer
> -
>
>
60 matches
Mail list logo
