See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/1031/changes
Changes:
[uschindler] make the script compatible with standard bourne shell. The problem
is that export and assignment does not work in this shell at the same time. But
the forrest path is not needed at all :-) - removed
benchmark alg can't handle negative relative priority
-
Key: LUCENE-2168
URL: https://issues.apache.org/jira/browse/LUCENE-2168
Project: Lucene - Java
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/LUCENE-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-2168.
Resolution: Fixed
benchmark alg can't handle negative relative priority
See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/1032/changes
Changes:
[uschindler] simplify build script and make more configureable
[mikemccand] add verbosity to intermittently failing test
--
[...truncated 19231 lines...]
[artifact:deploy]
Mike: when you come back from running, we need a new hudson run. Hopefully
the last one.
But this time everything worked until clover was about to be started. I hate
shell scripts and their strange \ syntax...
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
[
https://issues.apache.org/jira/browse/LUCENE-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-2034:
Attachment: LUCENE-2034.patch
robert, I updated your patch and moved stopawareAnalzyer to
[
https://issues.apache.org/jira/browse/LUCENE-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791896#action_12791896
]
Simon Willnauer edited comment on LUCENE-2034 at 12/17/09 12:31 PM:
[
https://issues.apache.org/jira/browse/LUCENE-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Willnauer updated LUCENE-2169:
Attachment: LUCENE-2169.patch
here is a patch
Speedup of CharArraySet#copy if a
Speedup of CharArraySet#copy if a CharArraySet instance is passed to copy.
--
Key: LUCENE-2169
URL: https://issues.apache.org/jira/browse/LUCENE-2169
Project: Lucene - Java
OK, back from running. Was insanely cold...
I just kicked off another build! Keep fingers crossed...
Mike
On Thu, Dec 17, 2009 at 7:07 AM, Uwe Schindler u...@thetaphi.de wrote:
Mike: when you come back from running, we need a new hudson run. Hopefully
the last one.
But this time
[
https://issues.apache.org/jira/browse/LUCENE-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791936#action_12791936
]
Michael McCandless commented on LUCENE-2026:
{quote}
FWIW, autoCommit doesn't
[
https://issues.apache.org/jira/browse/LUCENE-2035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791939#action_12791939
]
Mark Miller commented on LUCENE-2035:
-
I'll commit this soon.
[
https://issues.apache.org/jira/browse/LUCENE-1922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated LUCENE-1922:
Affects Version/s: (was: 2.4.1)
Flex Branch
exposing the ability to
[
https://issues.apache.org/jira/browse/LUCENE-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir reopened LUCENE-2080:
-
I am reopening this, because I have noticed lots of usage of LUCENE_CURRENT on
the user list, etc
[
https://issues.apache.org/jira/browse/LUCENE-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2080:
Fix Version/s: 2.9.2
Improve the documentation of Version
[
https://issues.apache.org/jira/browse/LUCENE-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791988#action_12791988
]
Michael McCandless commented on LUCENE-2080:
+1 to fix on 2.9.x
Improve the
See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/1033/changes
-
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
Hi all,
After multiple iterations and failed Hudson build, Mike and me got it
running:
We upgraded the build.xml and Hudson configuration to use now Clover 2.6.3
with a new license for Apache projects granted by Nick Pellow from
Atlassian. The new reports now cover all tests not only the
Uwe, do you know why the assert lines come through as not covered?
Are we not running w/ asserts enabled when we run with clover?
Mike
On Thu, Dec 17, 2009 at 1:25 PM, Uwe Schindler u...@thetaphi.de wrote:
Hi all,
After multiple iterations and failed Hudson build, Mike and me got it
running:
I will try this out later and add an always-failing assert to the code and
try with/without clover. I will add this as a test:
try {
assert false;
fail(asserts disabled)
} catch (AssertionFailedError e} {}
Maybe Nick can explain this to us. This was the same behaviour in clover
[
https://issues.apache.org/jira/browse/LUCENE-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1769:
--
Attachment: LUCENE-1769-2.patch
Improvements, will commit soon:
- separate core/contrib and
[
https://issues.apache.org/jira/browse/LUCENE-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shyamal Prasad updated LUCENE-2167:
---
Description:
The Javadoc for StandardTokenizer states:
{quote}
Splits words at punctuation
[
https://issues.apache.org/jira/browse/LUCENE-2167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12792271#action_12792271
]
Robert Muir commented on LUCENE-2167:
-
Hi Shyamal, I am not sure we should document
See http://hudson.zones.apache.org/hudson/job/Lucene-trunk/1034/changes
Changes:
[uschindler] LUCENE-1769: disable clover reports on assert statements
[uschindler] LUCENE-1769: Add also the opposite assert statement
[uschindler] LUCENE-1769: Improve clover analysis and separate core / bw
A new strange test failure:
[junit] Testcase:
testDuringAddDelete(org.apache.lucene.index.TestIndexWriterReader):
FAILED
[junit] null
[junit] junit.framework.AssertionFailedError: null
[junit] at
org.apache.lucene.index.TestIndexWriterReader.testDuringAddDelete(TestIndexW
A new strange test failure:
[junit] Testcase:
testDuringAddDelete(org.apache.lucene.index.TestIndexWriterReader):
FAILED
[junit] null
[junit] junit.framework.AssertionFailedError: null
[junit] at
org.apache.lucene.index.TestIndexWriterReader.testDuringAddDelete(TestInde
Here the patch, Mike, does this look ok?
When committed we can start a new Hudson run, if you like :-)
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: Uwe Schindler [mailto:u...@thetaphi.de]
Sent:
When looking around, TestStressIndexing has the same problem (only the time
is there 1.0 sec). Attached is a patch also for that. Also this test does
not use a volatile variable for the error boolean. Attached is a patch.
There are also other threads that may fail to do anything when the system
28 matches
Mail list logo
