otification regexes [was: RE: [JENKINS]
Lucene-Solr-4.x-Linux-Java6-64 - Build # 355 - Still Failing!]
FYI, we have a new check from LUCENE-4199, when it fails it looks like this:
[forbidden-apis] Scanned 5079 class file(s) for forbidden API
invocations (in 0.82s), 16 error(s).
BUILD FAILED
/h
Thanks Robert, I'll adjust the regexes. - Steve
-Original Message-
From: Robert Muir [mailto:rcm...@gmail.com]
Sent: Monday, July 09, 2012 11:42 AM
To: dev@lucene.apache.org
Subject: Re: Jenkins email notification regexes [was: RE: [JENKINS]
Lucene-Solr-4.x-Linux-Java6-64 - Build
that email notification isn't extracting stuff, let me know and
> I'll try to adjust the regexes.
>
> Steve
>
> -Original Message-
> From: Steven A Rowe [mailto:sar...@syr.edu]
> Sent: Monday, July 02, 2012 6:03 PM
> To: dev@lucene.apache.org
> Subject:
> I wasn't trying to complain,
I know but I should have thought of it myself.
Dawid
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
al Message-
From: dawid.we...@gmail.com [mailto:dawid.we...@gmail.com] On Behalf Of Dawid
Weiss
Sent: Sunday, July 08, 2012 2:08 AM
To: dev@lucene.apache.org
Subject: Re: Jenkins email notification regexes [was: RE: [JENKINS]
Lucene-Solr-4.x-Linux-Java6-64 - Build # 355 - Still Failing!]
> inte
> interesting stuff I know about. (E.g., [junit4] recently became
> [junit4:junit4].)
Damn, didn't think of it. This isn't anything I did -- I just used
junit4 as a library (with a namespace) to make things clearer which
things come from which bundle. Didn't think it'll affect ANT's logger
too,
x27;ll try to adjust the regexes.
Steve
-Original Message-
From: Steven A Rowe [mailto:sar...@syr.edu]
Sent: Monday, July 02, 2012 6:03 PM
To: dev@lucene.apache.org
Subject: RE: [JENKINS] Lucene-Solr-4.x-Linux-Java6-64 - Build # 355 - Still
Failing!
On Uwe's Jenkins, the regul
On Jul 2, 2012, at 8:20 PM, Michael McCandless wrote:
> On Mon, Jul 2, 2012 at 8:14 PM, Mark Miller wrote:
>>
>> On Jul 2, 2012, at 7:56 PM, Michael McCandless wrote:
>>
>>> Short story: I committed a fix (the javadocs for
>>> CloudState.getCollectionStates needed to escape the < and >).
>>
>>
On Mon, Jul 2, 2012 at 8:14 PM, Mark Miller wrote:
>
> On Jul 2, 2012, at 7:56 PM, Michael McCandless wrote:
>
>> Short story: I committed a fix (the javadocs for
>> CloudState.getCollectionStates needed to escape the < and >).
>
> Hmm, I couldn't get eclipse or ant javadocs to complain about this
On Jul 2, 2012, at 7:56 PM, Michael McCandless wrote:
> Short story: I committed a fix (the javadocs for
> CloudState.getCollectionStates needed to escape the < and >).
Hmm, I couldn't get eclipse or ant javadocs to complain about this (with my
java 1.6 or java 1.7 installs).
I wonder what I'm
On Mon, Jul 2, 2012 at 7:56 PM, Michael McCandless
wrote:
> Maybe we can find a more strict HTML parser
OK it turns out Python3's html.parser has an optional strict option...
and I confirmed that it would have caught this (and other), so, I
think we should use that.
But ... the Jenkins box
Short story: I committed a fix (the javadocs for
CloudState.getCollectionStates needed to escape the < and >).
Long story: at first I thought this was a javadocs bug ... and I
discovered that Python 2.7.3 gracefully ignores this while Python
2.7.2 freaks out about it.
So I upgraded Jenkins' Pytho
This is the one i suspect (with the workaround i used before):
http://www.lucidimagination.com/search/document/a4c5b64ef37774ff#e5fc87755f904b33
On Mon, Jul 2, 2012 at 5:56 PM, Robert Muir wrote:
> I've seen this before. The latest java6 builds have some javadocs bugs
> especially with generics
On Uwe's Jenkins, the regular expression used to extract failures for email
notification isn't pulling everything out that it should, e.g. this email is
missing javadocs-lint output.
I'm collecting examples of problems (failures to extract failures) and will
work on fixing some time this week.
I've seen this before. The latest java6 builds have some javadocs bugs
especially with generics. Locally with my java6u24 this all works
fine. Please ignore this for now, I'm sure its the same bug. I'll look
into it once i get the 4.0a stuff up on the website... (it likely
requires adding an except
15 matches
Mail list logo
