You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Erick Erickson <er...@gmail.com> on 2015/06/19 17:48:11 UTC
Any clue why I'm being asked to moderate these messages from the
build system?
Clearly they're coming from Elastic......
From: build@elastic.co
To: dev@elastic.co, dev@lucene.apache.org, simonw@apache.org
Cc:
Date: Fri, 19 Jun 2015 10:56:46 +0000
Subject: [CI] Lucene 5x Linux 64 Test Only - Build # 51986 - Failure!
BUILD FAILURE
Build URLhttp://build-eu-00.elastic.co/job/lucene_linux_java8_64_test_only/51986/
Project:lucene_linux_java8_64_test_only
Randomization:JDKEA9,local,heap[1024m],-server +UseConcMarkSweepGC
+UseCompressedOops +AggressiveOpts,sec manager on
Date of build:Fri, 19 Jun 2015 12:54:09 +0200
Build duration:2 min 35 sec
CHANGES
No Changes
BUILD ARTIFACTS
checkout/lucene/build/core/test/temp/junit4-J0-20150619_125429_116.events
checkout/lucene/build/core/test/temp/junit4-J1-20150619_125429_116.events
checkout/lucene/build/core/test/temp/junit4-J2-20150619_125429_112.events
checkout/lucene/build/core/test/temp/junit4-J3-20150619_125429_116.events
checkout/lucene/build/core/test/temp/junit4-J4-20150619_125429_112.events
checkout/lucene/build/core/test/temp/junit4-J5-20150619_125429_116.events
checkout/lucene/build/core/test/temp/junit4-J6-20150619_125429_118.events
checkout/lucene/build/core/test/temp/junit4-J7-20150619_125429_119.events
FAILED JUNIT TESTS
Name: junit.framework Failed: 2 test(s), Passed: 0 test(s), Skipped: 0
test(s), Total: 2 test(s)
Failed: junit.framework.TestSuite.org.apache.lucene.search.TestNumericRangeQuery32
Failed: junit.framework.TestSuite.org.apache.lucene.search.TestNumericRangeQuery32
Name: org.apache.lucene.index Failed: 2 test(s), Passed: 774 test(s),
Skipped: 23 test(s), Total: 799 test(s)
Failed: org.apache.lucene.index.TestIndexWriterExceptions.testAddDocsNonAbortingException
Failed: org.apache.lucene.index.TestIndexWriterExceptions.testExceptionFromTokenStream
CONSOLE OUTPUT
[...truncated 1849 lines...]
[junit4] - org.apache.lucene.index.TestIndexWriterExceptions.testExceptionFromTokenStream
[junit4] - org.apache.lucene.index.TestIndexWriterExceptions.testAddDocsNonAbortingException
[junit4]
[junit4]
[junit4] JVM J0: 1.02 .. 125.17 = 124.15s
[junit4] JVM J1: 1.01 .. 124.41 = 123.39s
[junit4] JVM J2: 1.33 .. 124.50 = 123.17s
[junit4] JVM J3: 1.11 .. 122.66 = 121.55s
[junit4] JVM J4: 1.24 .. 124.04 = 122.80s
[junit4] JVM J5: 1.01 .. 127.16 = 126.15s
[junit4] JVM J6: 1.00 .. 133.45 = 132.45s
[junit4] JVM J7: 1.03 .. 125.12 = 124.08s
[junit4] Execution time total: 2 minutes 13 seconds
[junit4] Tests summary: 401 suites, 3227 tests, 2 suite-level errors,
2 errors, 48 ignored (44 assumptions)
BUILD FAILED
/home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/build.xml:50:
The following error occurred while executing this line:
/home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/common-build.xml:1444:
The following error occurred while executing this line:
/home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/common-build.xml:999:
There were test failures: 401 suites, 3227 tests, 2 suite-level
errors, 2 errors, 48 ignored (44 assumptions)
Total time: 2 minutes 21 seconds
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Michael McCandless <lu...@mikemccandless.com>.
On Wed, Sep 9, 2015 at 9:28 AM, Upayavira <uv...@odoko.co.uk> wrote:
> build@elastic.co *is* on the allow list for dev, so dunno why it is in
> the moderation queue.
Phew, we need a mailing-list-debugger.
> If people are okay with it, I'll add myself as a list moderator and see
> if I can make anything of the moderation messages. Any objections?
Yes please! Thank you for helping out Upayavira!
Mike McCandless
http://blog.mikemccandless.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Upayavira <uv...@odoko.co.uk>.
Thx Hoss! Seems it is already in hand (or understood at least)
On Wed, Sep 9, 2015, at 03:38 PM, Chris Hostetter wrote:
>
> : Every individual email "From: build@elastic.co" is usually a completley
> : distinct "Return-Path" header...
> ...
> : ...these addresses are what get compared against hte subscription lists
> : (and auot-alowed whitelists).
>
> Acctually ... just to clarify: ezmlm verifies
> subscription/whitelisting/blacklisting against the SMTP "sender" info
> from
> the SMTP envelope -- it doesn't check the Return-path header directly.
>
> But in all of the cases i looked at where these build@elastic.co are
> stuck
> in the moderation queue, the addr that was being asked for moderation
> (from the envelope) matched the (UUID-ish) Return-Path header (from the
> message).
>
> ie: the variable Return-Path headers appears to be *symptom* of how the
> SMTP sender is being set to a unique addr everytime, but the envelope
> itself needs fixed to use a consistent address, not just the Return-Path.
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Michael McCandless <lu...@mikemccandless.com>.
OK I think we (ES) have fixed the outgoing Jenkins failure emails to
use a "sane" Return-Path SMTP header ... if anyone still sees ES
Jenkins failures emails requiring moderation please let me know!
Thanks.
Mike McCandless
http://blog.mikemccandless.com
On Wed, Sep 9, 2015 at 4:17 PM, Michael McCandless
<lu...@mikemccandless.com> wrote:
> Ahhh, OK thanks for explaining the situation Hoss. I'll talk to Simon
> to see how/if we can fix this craziness.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Wed, Sep 9, 2015 at 10:38 AM, Chris Hostetter
> <ho...@fucit.org> wrote:
>>
>> : Every individual email "From: build@elastic.co" is usually a completley
>> : distinct "Return-Path" header...
>> ...
>> : ...these addresses are what get compared against hte subscription lists
>> : (and auot-alowed whitelists).
>>
>> Acctually ... just to clarify: ezmlm verifies
>> subscription/whitelisting/blacklisting against the SMTP "sender" info from
>> the SMTP envelope -- it doesn't check the Return-path header directly.
>>
>> But in all of the cases i looked at where these build@elastic.co are stuck
>> in the moderation queue, the addr that was being asked for moderation
>> (from the envelope) matched the (UUID-ish) Return-Path header (from the
>> message).
>>
>> ie: the variable Return-Path headers appears to be *symptom* of how the
>> SMTP sender is being set to a unique addr everytime, but the envelope
>> itself needs fixed to use a consistent address, not just the Return-Path.
>>
>>
>> -Hoss
>> http://www.lucidworks.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Michael McCandless <lu...@mikemccandless.com>.
Ahhh, OK thanks for explaining the situation Hoss. I'll talk to Simon
to see how/if we can fix this craziness.
Mike McCandless
http://blog.mikemccandless.com
On Wed, Sep 9, 2015 at 10:38 AM, Chris Hostetter
<ho...@fucit.org> wrote:
>
> : Every individual email "From: build@elastic.co" is usually a completley
> : distinct "Return-Path" header...
> ...
> : ...these addresses are what get compared against hte subscription lists
> : (and auot-alowed whitelists).
>
> Acctually ... just to clarify: ezmlm verifies
> subscription/whitelisting/blacklisting against the SMTP "sender" info from
> the SMTP envelope -- it doesn't check the Return-path header directly.
>
> But in all of the cases i looked at where these build@elastic.co are stuck
> in the moderation queue, the addr that was being asked for moderation
> (from the envelope) matched the (UUID-ish) Return-Path header (from the
> message).
>
> ie: the variable Return-Path headers appears to be *symptom* of how the
> SMTP sender is being set to a unique addr everytime, but the envelope
> itself needs fixed to use a consistent address, not just the Return-Path.
>
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from
the build system?
Posted by Chris Hostetter <ho...@fucit.org>.
: Every individual email "From: build@elastic.co" is usually a completley
: distinct "Return-Path" header...
...
: ...these addresses are what get compared against hte subscription lists
: (and auot-alowed whitelists).
Acctually ... just to clarify: ezmlm verifies
subscription/whitelisting/blacklisting against the SMTP "sender" info from
the SMTP envelope -- it doesn't check the Return-path header directly.
But in all of the cases i looked at where these build@elastic.co are stuck
in the moderation queue, the addr that was being asked for moderation
(from the envelope) matched the (UUID-ish) Return-Path header (from the
message).
ie: the variable Return-Path headers appears to be *symptom* of how the
SMTP sender is being set to a unique addr everytime, but the envelope
itself needs fixed to use a consistent address, not just the Return-Path.
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from
the build system?
Posted by Chris Hostetter <ho...@fucit.org>.
: build@elastic.co *is* on the allow list for dev, so dunno why it is in
: the moderation queue.
As discussed before on the dev-owner list (for the specific purpose of not
distracting the entire dev community with mailing list management issues
-- but alas, since it keeps coming up here i'll repeat) the problem is
that the build@elastic.co emails are only using "build@elastic.co" as the
*From* addr -- which is largely meaningless in modern mail software these
days.
Every individual email "From: build@elastic.co" is usually a completley
distinct "Return-Path" header...
Return-Path: <00...@amazonses.com>
...
Return-Path: <00...@amazonses.com>
...
Return-Path: <00...@amazonses.com>
...
...these addresses are what get compared against hte subscription lists
(and auot-alowed whitelists).
This information was already discusssed with simon, who said he would talk
to the relevant people in control of build@elastic.co to get this fixed --
but that was in June and there haven't been any replies (to that
dev-owner thread) since.
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Upayavira <uv...@odoko.co.uk>.
build@elastic.co *is* on the allow list for dev, so dunno why it is in
the moderation queue.
If people are okay with it, I'll add myself as a list moderator and see
if I can make anything of the moderation messages. Any objections?
Upayavira
On Wed, Sep 9, 2015, at 01:58 PM, Michael McCandless wrote:
> It looks like the Jenkins build failures from build@elastic.co are
> still requiring moderation ...
>
> Upayavira or Uwe, can you re-check and confirm that build@elastic.co
> really is successfully subscribed to dev@lucene.apache.org? Thanks.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sun, Jul 12, 2015 at 3:48 PM, Michael McCandless
> <lu...@mikemccandless.com> wrote:
> > On Sun, Jul 12, 2015 at 3:47 PM, Upayavira <uv...@odoko.co.uk> wrote:
> >> I'm sure that's something I could easily bring about, if it helps!
> >
> > Oh it happens quite effectively on its own :) But thank you for the offer!
> >
> > Mike McCandless
> >
> > http://blog.mikemccandless.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Michael McCandless <lu...@mikemccandless.com>.
It looks like the Jenkins build failures from build@elastic.co are
still requiring moderation ...
Upayavira or Uwe, can you re-check and confirm that build@elastic.co
really is successfully subscribed to dev@lucene.apache.org? Thanks.
Mike McCandless
http://blog.mikemccandless.com
On Sun, Jul 12, 2015 at 3:48 PM, Michael McCandless
<lu...@mikemccandless.com> wrote:
> On Sun, Jul 12, 2015 at 3:47 PM, Upayavira <uv...@odoko.co.uk> wrote:
>> I'm sure that's something I could easily bring about, if it helps!
>
> Oh it happens quite effectively on its own :) But thank you for the offer!
>
> Mike McCandless
>
> http://blog.mikemccandless.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Michael McCandless <lu...@mikemccandless.com>.
On Sun, Jul 12, 2015 at 3:47 PM, Upayavira <uv...@odoko.co.uk> wrote:
> I'm sure that's something I could easily bring about, if it helps!
Oh it happens quite effectively on its own :) But thank you for the offer!
Mike McCandless
http://blog.mikemccandless.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Upayavira <uv...@odoko.co.uk>.
I'm sure that's something I could easily bring about, if it helps!
On Sun, Jul 12, 2015, at 08:32 PM, Michael McCandless wrote:
> Thanks Upayavira!
>
> Now we wait for a build failure :)
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Sun, Jul 12, 2015 at 3:21 PM, Upayavira <uv...@odoko.co.uk> wrote:
> > Due to my (long ago) history with infra, I still have apmail privileges.
> >
> > I have subscribed build@elastic.co to the dev@lucene.apache.org allow
> > list which should solve this. I could see that it wasn't there before I
> > did so.
> >
> > Upayavira
> >
> > On Sun, Jul 12, 2015, at 07:06 PM, Michael McCandless wrote:
> >> On Sun, Jul 12, 2015 at 1:51 PM, Uwe Schindler <uw...@thetaphi.de> wrote:
> >>
> >> > We should simply forcefully subscribe this address to dev@. The reason why Reply-All does not work is caused by Amazon's mail servers who use a different header on each mail.
> >>
> >> Hmm, OK, but we can separately try to address this somehow?
> >>
> >> > Should I forcefully subscribe this address (have rights to do this)?
> >>
> >> +1, thank you!
> >>
> >> > The only backside: build@elastic.co would then get all mailing list traffic - if this is no problem this would be easiest!
> >>
> >> Let's try and see: easier to ask forgiveness than permission!
> >>
> >> Thanks Uwe!
> >>
> >> Mike McCandless
> >>
> >> http://blog.mikemccandless.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >> For additional commands, e-mail: dev-help@lucene.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: dev-help@lucene.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Michael McCandless <lu...@mikemccandless.com>.
Thanks Upayavira!
Now we wait for a build failure :)
Mike McCandless
http://blog.mikemccandless.com
On Sun, Jul 12, 2015 at 3:21 PM, Upayavira <uv...@odoko.co.uk> wrote:
> Due to my (long ago) history with infra, I still have apmail privileges.
>
> I have subscribed build@elastic.co to the dev@lucene.apache.org allow
> list which should solve this. I could see that it wasn't there before I
> did so.
>
> Upayavira
>
> On Sun, Jul 12, 2015, at 07:06 PM, Michael McCandless wrote:
>> On Sun, Jul 12, 2015 at 1:51 PM, Uwe Schindler <uw...@thetaphi.de> wrote:
>>
>> > We should simply forcefully subscribe this address to dev@. The reason why Reply-All does not work is caused by Amazon's mail servers who use a different header on each mail.
>>
>> Hmm, OK, but we can separately try to address this somehow?
>>
>> > Should I forcefully subscribe this address (have rights to do this)?
>>
>> +1, thank you!
>>
>> > The only backside: build@elastic.co would then get all mailing list traffic - if this is no problem this would be easiest!
>>
>> Let's try and see: easier to ask forgiveness than permission!
>>
>> Thanks Uwe!
>>
>> Mike McCandless
>>
>> http://blog.mikemccandless.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Upayavira <uv...@odoko.co.uk>.
Due to my (long ago) history with infra, I still have apmail privileges.
I have subscribed build@elastic.co to the dev@lucene.apache.org allow
list which should solve this. I could see that it wasn't there before I
did so.
Upayavira
On Sun, Jul 12, 2015, at 07:06 PM, Michael McCandless wrote:
> On Sun, Jul 12, 2015 at 1:51 PM, Uwe Schindler <uw...@thetaphi.de> wrote:
>
> > We should simply forcefully subscribe this address to dev@. The reason why Reply-All does not work is caused by Amazon's mail servers who use a different header on each mail.
>
> Hmm, OK, but we can separately try to address this somehow?
>
> > Should I forcefully subscribe this address (have rights to do this)?
>
> +1, thank you!
>
> > The only backside: build@elastic.co would then get all mailing list traffic - if this is no problem this would be easiest!
>
> Let's try and see: easier to ask forgiveness than permission!
>
> Thanks Uwe!
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Michael McCandless <lu...@mikemccandless.com>.
On Sun, Jul 12, 2015 at 1:51 PM, Uwe Schindler <uw...@thetaphi.de> wrote:
> We should simply forcefully subscribe this address to dev@. The reason why Reply-All does not work is caused by Amazon's mail servers who use a different header on each mail.
Hmm, OK, but we can separately try to address this somehow?
> Should I forcefully subscribe this address (have rights to do this)?
+1, thank you!
> The only backside: build@elastic.co would then get all mailing list traffic - if this is no problem this would be easiest!
Let's try and see: easier to ask forgiveness than permission!
Thanks Uwe!
Mike McCandless
http://blog.mikemccandless.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
RE: Any clue why I'm being asked to moderate these messages from the build system?
Posted by Uwe Schindler <uw...@thetaphi.de>.
Hi,
We should simply forcefully subscribe this address to dev@. The reason why Reply-All does not work is caused by Amazon's mail servers who use a different header on each mail.
Should I forcefully subscribe this address (have rights to do this)? Just have to lookup the special mail address to do this. The only backside: build@elastic.co would then get all mailing list traffic - if this is no problem this would be easiest!
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: uwe@thetaphi.de
> -----Original Message-----
> From: Michael McCandless [mailto:lucene@mikemccandless.com]
> Sent: Sunday, July 12, 2015 7:44 PM
> To: Lucene/Solr dev
> Subject: Re: Any clue why I'm being asked to moderate these messages from
> the build system?
>
> I'd like to fix this: it seems silly you all have to moderate these build failures.
>
> Is it as simple as forcefully subscribing "build@elastic.co" to the dev list?
> Does someone know how to do this :)
>
> Except, Uwe mentioned something about maybe needing a specific Jenkins
> plugin as well...?
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Fri, Jun 19, 2015 at 1:52 PM, Steve Rowe <sa...@gmail.com> wrote:
> > I’ve reply-all’d to a bunch of these from the moderation queue, but they
> still seem to require moderation though.
> >
> >> On Jun 19, 2015, at 1:41 PM, Erick Erickson <er...@gmail.com>
> wrote:
> >>
> >> Right, but I keep getting them even after approving some of them.
> >> It's like the from address keeps changing.
> >>
> >> Or I'm just confused. I'll "reply-all" for a while and we'll see.
> >>
> >> On Fri, Jun 19, 2015 at 9:55 AM, Chris Hostetter
> >> <ho...@fucit.org> wrote:
> >>>
> >>> : Clearly they're coming from Elastic......
> >>>
> >>> pretty sure it's just standard moderatation queue stuff...
> >>>
> >>> the first time a (non-subscribed) addr sends an email to the list,
> >>> it gets held in the queue -- if the moderator just hits "reply" tothe
> "accept"
> >>> address, then that one message will make it through -- but future
> >>> messages will not.
> >>>
> >>> Which is why moderators are encouraged to "reply-all" so that the
> "allow"
> >>> address is also hit -- this ensures that future messages from the
> >>> same sender won't get stuck in the moderation queue in the future.
> >>>
> >>> at some point recently elastic changed the email addr used by their
> >>> CI system, so it needed to be re-allowed to send mail, and they
> >>> started popping back up in the moderation queue.
> >>>
> >>> (As a reminder: questions like this are why we have the moderator
> >>> list, so we don't have to distract the entire dev community with
> >>> meta-discussions about dealing with moderation)
> >>>
> >>>
> >>> :
> >>> : From: build@elastic.co
> >>> : To: dev@elastic.co, dev@lucene.apache.org, simonw@apache.org
> >>> : Cc:
> >>> : Date: Fri, 19 Jun 2015 10:56:46 +0000
> >>> : Subject: [CI] Lucene 5x Linux 64 Test Only - Build # 51986 - Failure!
> >>> : BUILD FAILURE
> >>> :
> >>> : Build
> >>> URLhttp://build-eu-00.elastic.co/job/lucene_linux_java8_64_test_only
> >>> /51986/
> >>> : Project:lucene_linux_java8_64_test_only
> >>> : Randomization:JDKEA9,local,heap[1024m],-server
> +UseConcMarkSweepGC
> >>> : +UseCompressedOops +AggressiveOpts,sec manager on
> >>> : Date of build:Fri, 19 Jun 2015 12:54:09 +0200
> >>> : Build duration:2 min 35 sec
> >>> :
> >>> : CHANGES
> >>> : No Changes
> >>> :
> >>> : BUILD ARTIFACTS
> >>> :
> >>> checkout/lucene/build/core/test/temp/junit4-J0-
> 20150619_125429_116.e
> >>> vents
> >>> :
> >>> checkout/lucene/build/core/test/temp/junit4-J1-
> 20150619_125429_116.e
> >>> vents
> >>> :
> >>> checkout/lucene/build/core/test/temp/junit4-J2-
> 20150619_125429_112.e
> >>> vents
> >>> :
> >>> checkout/lucene/build/core/test/temp/junit4-J3-
> 20150619_125429_116.e
> >>> vents
> >>> :
> >>> checkout/lucene/build/core/test/temp/junit4-J4-
> 20150619_125429_112.e
> >>> vents
> >>> :
> >>> checkout/lucene/build/core/test/temp/junit4-J5-
> 20150619_125429_116.e
> >>> vents
> >>> :
> >>> checkout/lucene/build/core/test/temp/junit4-J6-
> 20150619_125429_118.e
> >>> vents
> >>> :
> >>> checkout/lucene/build/core/test/temp/junit4-J7-
> 20150619_125429_119.e
> >>> vents
> >>> :
> >>> : FAILED JUNIT TESTS
> >>> : Name: junit.framework Failed: 2 test(s), Passed: 0 test(s),
> >>> Skipped: 0
> >>> : test(s), Total: 2 test(s)
> >>> : Failed:
> >>>
> junit.framework.TestSuite.org.apache.lucene.search.TestNumericRangeQ
> >>> uery32
> >>> : Failed:
> >>>
> junit.framework.TestSuite.org.apache.lucene.search.TestNumericRangeQ
> >>> uery32
> >>> : Name: org.apache.lucene.index Failed: 2 test(s), Passed: 774
> >>> test(s),
> >>> : Skipped: 23 test(s), Total: 799 test(s)
> >>> : Failed:
> >>>
> org.apache.lucene.index.TestIndexWriterExceptions.testAddDocsNonAbor
> >>> tingException
> >>> : Failed:
> >>>
> org.apache.lucene.index.TestIndexWriterExceptions.testExceptionFromT
> >>> okenStream
> >>> :
> >>> : CONSOLE OUTPUT
> >>> : [...truncated 1849 lines...]
> >>> : [junit4] -
> >>>
> org.apache.lucene.index.TestIndexWriterExceptions.testExceptionFromT
> >>> okenStream
> >>> : [junit4] -
> >>>
> org.apache.lucene.index.TestIndexWriterExceptions.testAddDocsNonAbor
> >>> tingException
> >>> : [junit4]
> >>> : [junit4]
> >>> : [junit4] JVM J0: 1.02 .. 125.17 = 124.15s
> >>> : [junit4] JVM J1: 1.01 .. 124.41 = 123.39s
> >>> : [junit4] JVM J2: 1.33 .. 124.50 = 123.17s
> >>> : [junit4] JVM J3: 1.11 .. 122.66 = 121.55s
> >>> : [junit4] JVM J4: 1.24 .. 124.04 = 122.80s
> >>> : [junit4] JVM J5: 1.01 .. 127.16 = 126.15s
> >>> : [junit4] JVM J6: 1.00 .. 133.45 = 132.45s
> >>> : [junit4] JVM J7: 1.03 .. 125.12 = 124.08s
> >>> : [junit4] Execution time total: 2 minutes 13 seconds
> >>> : [junit4] Tests summary: 401 suites, 3227 tests, 2 suite-level
> >>> errors,
> >>> : 2 errors, 48 ignored (44 assumptions)
> >>> : BUILD FAILED
> >>> :
> /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/luce
> ne/build.xml:50:
> >>> : The following error occurred while executing this line:
> >>> :
> /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/luce
> ne/common-build.xml:1444:
> >>> : The following error occurred while executing this line:
> >>> :
> /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/luce
> ne/common-build.xml:999:
> >>> : There were test failures: 401 suites, 3227 tests, 2 suite-level
> >>> : errors, 2 errors, 48 ignored (44 assumptions)
> >>> : Total time: 2 minutes 21 seconds
> >>> :
> >>> :
> >>> --------------------------------------------------------------------
> >>> -
> >>> : To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> >>> : For additional commands, e-mail: dev-help@lucene.apache.org
> >>> :
> >>> :
> >>>
> >>> -Hoss
> >>> http://www.lucidworks.com/
> >>>
> >>> --------------------------------------------------------------------
> >>> - To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For
> >>> additional commands, e-mail: dev-help@lucene.apache.org
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For
> >> additional commands, e-mail: dev-help@lucene.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For
> > additional commands, e-mail: dev-help@lucene.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional
> commands, e-mail: dev-help@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Michael McCandless <lu...@mikemccandless.com>.
I'd like to fix this: it seems silly you all have to moderate these
build failures.
Is it as simple as forcefully subscribing "build@elastic.co" to the
dev list? Does someone know how to do this :)
Except, Uwe mentioned something about maybe needing a specific Jenkins
plugin as well...?
Mike McCandless
http://blog.mikemccandless.com
On Fri, Jun 19, 2015 at 1:52 PM, Steve Rowe <sa...@gmail.com> wrote:
> I’ve reply-all’d to a bunch of these from the moderation queue, but they still seem to require moderation though.
>
>> On Jun 19, 2015, at 1:41 PM, Erick Erickson <er...@gmail.com> wrote:
>>
>> Right, but I keep getting them even after approving some of them. It's
>> like the from address keeps changing.
>>
>> Or I'm just confused. I'll "reply-all" for a while and we'll see.
>>
>> On Fri, Jun 19, 2015 at 9:55 AM, Chris Hostetter
>> <ho...@fucit.org> wrote:
>>>
>>> : Clearly they're coming from Elastic......
>>>
>>> pretty sure it's just standard moderatation queue stuff...
>>>
>>> the first time a (non-subscribed) addr sends an email to the list, it gets
>>> held in the queue -- if the moderator just hits "reply" tothe "accept"
>>> address, then that one message will make it through -- but future messages
>>> will not.
>>>
>>> Which is why moderators are encouraged to "reply-all" so that the "allow"
>>> address is also hit -- this ensures that future messages from the same
>>> sender won't get stuck in the moderation queue in the future.
>>>
>>> at some point recently elastic changed the email addr used by their CI
>>> system, so it needed to be re-allowed to send mail, and they started
>>> popping back up in the moderation queue.
>>>
>>> (As a reminder: questions like this are why we have the moderator list, so
>>> we don't have to distract the entire dev community with meta-discussions
>>> about dealing with moderation)
>>>
>>>
>>> :
>>> : From: build@elastic.co
>>> : To: dev@elastic.co, dev@lucene.apache.org, simonw@apache.org
>>> : Cc:
>>> : Date: Fri, 19 Jun 2015 10:56:46 +0000
>>> : Subject: [CI] Lucene 5x Linux 64 Test Only - Build # 51986 - Failure!
>>> : BUILD FAILURE
>>> :
>>> : Build URLhttp://build-eu-00.elastic.co/job/lucene_linux_java8_64_test_only/51986/
>>> : Project:lucene_linux_java8_64_test_only
>>> : Randomization:JDKEA9,local,heap[1024m],-server +UseConcMarkSweepGC
>>> : +UseCompressedOops +AggressiveOpts,sec manager on
>>> : Date of build:Fri, 19 Jun 2015 12:54:09 +0200
>>> : Build duration:2 min 35 sec
>>> :
>>> : CHANGES
>>> : No Changes
>>> :
>>> : BUILD ARTIFACTS
>>> : checkout/lucene/build/core/test/temp/junit4-J0-20150619_125429_116.events
>>> : checkout/lucene/build/core/test/temp/junit4-J1-20150619_125429_116.events
>>> : checkout/lucene/build/core/test/temp/junit4-J2-20150619_125429_112.events
>>> : checkout/lucene/build/core/test/temp/junit4-J3-20150619_125429_116.events
>>> : checkout/lucene/build/core/test/temp/junit4-J4-20150619_125429_112.events
>>> : checkout/lucene/build/core/test/temp/junit4-J5-20150619_125429_116.events
>>> : checkout/lucene/build/core/test/temp/junit4-J6-20150619_125429_118.events
>>> : checkout/lucene/build/core/test/temp/junit4-J7-20150619_125429_119.events
>>> :
>>> : FAILED JUNIT TESTS
>>> : Name: junit.framework Failed: 2 test(s), Passed: 0 test(s), Skipped: 0
>>> : test(s), Total: 2 test(s)
>>> : Failed: junit.framework.TestSuite.org.apache.lucene.search.TestNumericRangeQuery32
>>> : Failed: junit.framework.TestSuite.org.apache.lucene.search.TestNumericRangeQuery32
>>> : Name: org.apache.lucene.index Failed: 2 test(s), Passed: 774 test(s),
>>> : Skipped: 23 test(s), Total: 799 test(s)
>>> : Failed: org.apache.lucene.index.TestIndexWriterExceptions.testAddDocsNonAbortingException
>>> : Failed: org.apache.lucene.index.TestIndexWriterExceptions.testExceptionFromTokenStream
>>> :
>>> : CONSOLE OUTPUT
>>> : [...truncated 1849 lines...]
>>> : [junit4] - org.apache.lucene.index.TestIndexWriterExceptions.testExceptionFromTokenStream
>>> : [junit4] - org.apache.lucene.index.TestIndexWriterExceptions.testAddDocsNonAbortingException
>>> : [junit4]
>>> : [junit4]
>>> : [junit4] JVM J0: 1.02 .. 125.17 = 124.15s
>>> : [junit4] JVM J1: 1.01 .. 124.41 = 123.39s
>>> : [junit4] JVM J2: 1.33 .. 124.50 = 123.17s
>>> : [junit4] JVM J3: 1.11 .. 122.66 = 121.55s
>>> : [junit4] JVM J4: 1.24 .. 124.04 = 122.80s
>>> : [junit4] JVM J5: 1.01 .. 127.16 = 126.15s
>>> : [junit4] JVM J6: 1.00 .. 133.45 = 132.45s
>>> : [junit4] JVM J7: 1.03 .. 125.12 = 124.08s
>>> : [junit4] Execution time total: 2 minutes 13 seconds
>>> : [junit4] Tests summary: 401 suites, 3227 tests, 2 suite-level errors,
>>> : 2 errors, 48 ignored (44 assumptions)
>>> : BUILD FAILED
>>> : /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/build.xml:50:
>>> : The following error occurred while executing this line:
>>> : /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/common-build.xml:1444:
>>> : The following error occurred while executing this line:
>>> : /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/common-build.xml:999:
>>> : There were test failures: 401 suites, 3227 tests, 2 suite-level
>>> : errors, 2 errors, 48 ignored (44 assumptions)
>>> : Total time: 2 minutes 21 seconds
>>> :
>>> : ---------------------------------------------------------------------
>>> : To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> : For additional commands, e-mail: dev-help@lucene.apache.org
>>> :
>>> :
>>>
>>> -Hoss
>>> http://www.lucidworks.com/
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>>> For additional commands, e-mail: dev-help@lucene.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the build system?
Posted by Steve Rowe <sa...@gmail.com>.
I’ve reply-all’d to a bunch of these from the moderation queue, but they still seem to require moderation though.
> On Jun 19, 2015, at 1:41 PM, Erick Erickson <er...@gmail.com> wrote:
>
> Right, but I keep getting them even after approving some of them. It's
> like the from address keeps changing.
>
> Or I'm just confused. I'll "reply-all" for a while and we'll see.
>
> On Fri, Jun 19, 2015 at 9:55 AM, Chris Hostetter
> <ho...@fucit.org> wrote:
>>
>> : Clearly they're coming from Elastic......
>>
>> pretty sure it's just standard moderatation queue stuff...
>>
>> the first time a (non-subscribed) addr sends an email to the list, it gets
>> held in the queue -- if the moderator just hits "reply" tothe "accept"
>> address, then that one message will make it through -- but future messages
>> will not.
>>
>> Which is why moderators are encouraged to "reply-all" so that the "allow"
>> address is also hit -- this ensures that future messages from the same
>> sender won't get stuck in the moderation queue in the future.
>>
>> at some point recently elastic changed the email addr used by their CI
>> system, so it needed to be re-allowed to send mail, and they started
>> popping back up in the moderation queue.
>>
>> (As a reminder: questions like this are why we have the moderator list, so
>> we don't have to distract the entire dev community with meta-discussions
>> about dealing with moderation)
>>
>>
>> :
>> : From: build@elastic.co
>> : To: dev@elastic.co, dev@lucene.apache.org, simonw@apache.org
>> : Cc:
>> : Date: Fri, 19 Jun 2015 10:56:46 +0000
>> : Subject: [CI] Lucene 5x Linux 64 Test Only - Build # 51986 - Failure!
>> : BUILD FAILURE
>> :
>> : Build URLhttp://build-eu-00.elastic.co/job/lucene_linux_java8_64_test_only/51986/
>> : Project:lucene_linux_java8_64_test_only
>> : Randomization:JDKEA9,local,heap[1024m],-server +UseConcMarkSweepGC
>> : +UseCompressedOops +AggressiveOpts,sec manager on
>> : Date of build:Fri, 19 Jun 2015 12:54:09 +0200
>> : Build duration:2 min 35 sec
>> :
>> : CHANGES
>> : No Changes
>> :
>> : BUILD ARTIFACTS
>> : checkout/lucene/build/core/test/temp/junit4-J0-20150619_125429_116.events
>> : checkout/lucene/build/core/test/temp/junit4-J1-20150619_125429_116.events
>> : checkout/lucene/build/core/test/temp/junit4-J2-20150619_125429_112.events
>> : checkout/lucene/build/core/test/temp/junit4-J3-20150619_125429_116.events
>> : checkout/lucene/build/core/test/temp/junit4-J4-20150619_125429_112.events
>> : checkout/lucene/build/core/test/temp/junit4-J5-20150619_125429_116.events
>> : checkout/lucene/build/core/test/temp/junit4-J6-20150619_125429_118.events
>> : checkout/lucene/build/core/test/temp/junit4-J7-20150619_125429_119.events
>> :
>> : FAILED JUNIT TESTS
>> : Name: junit.framework Failed: 2 test(s), Passed: 0 test(s), Skipped: 0
>> : test(s), Total: 2 test(s)
>> : Failed: junit.framework.TestSuite.org.apache.lucene.search.TestNumericRangeQuery32
>> : Failed: junit.framework.TestSuite.org.apache.lucene.search.TestNumericRangeQuery32
>> : Name: org.apache.lucene.index Failed: 2 test(s), Passed: 774 test(s),
>> : Skipped: 23 test(s), Total: 799 test(s)
>> : Failed: org.apache.lucene.index.TestIndexWriterExceptions.testAddDocsNonAbortingException
>> : Failed: org.apache.lucene.index.TestIndexWriterExceptions.testExceptionFromTokenStream
>> :
>> : CONSOLE OUTPUT
>> : [...truncated 1849 lines...]
>> : [junit4] - org.apache.lucene.index.TestIndexWriterExceptions.testExceptionFromTokenStream
>> : [junit4] - org.apache.lucene.index.TestIndexWriterExceptions.testAddDocsNonAbortingException
>> : [junit4]
>> : [junit4]
>> : [junit4] JVM J0: 1.02 .. 125.17 = 124.15s
>> : [junit4] JVM J1: 1.01 .. 124.41 = 123.39s
>> : [junit4] JVM J2: 1.33 .. 124.50 = 123.17s
>> : [junit4] JVM J3: 1.11 .. 122.66 = 121.55s
>> : [junit4] JVM J4: 1.24 .. 124.04 = 122.80s
>> : [junit4] JVM J5: 1.01 .. 127.16 = 126.15s
>> : [junit4] JVM J6: 1.00 .. 133.45 = 132.45s
>> : [junit4] JVM J7: 1.03 .. 125.12 = 124.08s
>> : [junit4] Execution time total: 2 minutes 13 seconds
>> : [junit4] Tests summary: 401 suites, 3227 tests, 2 suite-level errors,
>> : 2 errors, 48 ignored (44 assumptions)
>> : BUILD FAILED
>> : /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/build.xml:50:
>> : The following error occurred while executing this line:
>> : /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/common-build.xml:1444:
>> : The following error occurred while executing this line:
>> : /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/common-build.xml:999:
>> : There were test failures: 401 suites, 3227 tests, 2 suite-level
>> : errors, 2 errors, 48 ignored (44 assumptions)
>> : Total time: 2 minutes 21 seconds
>> :
>> : ---------------------------------------------------------------------
>> : To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> : For additional commands, e-mail: dev-help@lucene.apache.org
>> :
>> :
>>
>> -Hoss
>> http://www.lucidworks.com/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: dev-help@lucene.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from the
build system?
Posted by Erick Erickson <er...@gmail.com>.
Right, but I keep getting them even after approving some of them. It's
like the from address keeps changing.
Or I'm just confused. I'll "reply-all" for a while and we'll see.
On Fri, Jun 19, 2015 at 9:55 AM, Chris Hostetter
<ho...@fucit.org> wrote:
>
> : Clearly they're coming from Elastic......
>
> pretty sure it's just standard moderatation queue stuff...
>
> the first time a (non-subscribed) addr sends an email to the list, it gets
> held in the queue -- if the moderator just hits "reply" tothe "accept"
> address, then that one message will make it through -- but future messages
> will not.
>
> Which is why moderators are encouraged to "reply-all" so that the "allow"
> address is also hit -- this ensures that future messages from the same
> sender won't get stuck in the moderation queue in the future.
>
> at some point recently elastic changed the email addr used by their CI
> system, so it needed to be re-allowed to send mail, and they started
> popping back up in the moderation queue.
>
> (As a reminder: questions like this are why we have the moderator list, so
> we don't have to distract the entire dev community with meta-discussions
> about dealing with moderation)
>
>
> :
> : From: build@elastic.co
> : To: dev@elastic.co, dev@lucene.apache.org, simonw@apache.org
> : Cc:
> : Date: Fri, 19 Jun 2015 10:56:46 +0000
> : Subject: [CI] Lucene 5x Linux 64 Test Only - Build # 51986 - Failure!
> : BUILD FAILURE
> :
> : Build URLhttp://build-eu-00.elastic.co/job/lucene_linux_java8_64_test_only/51986/
> : Project:lucene_linux_java8_64_test_only
> : Randomization:JDKEA9,local,heap[1024m],-server +UseConcMarkSweepGC
> : +UseCompressedOops +AggressiveOpts,sec manager on
> : Date of build:Fri, 19 Jun 2015 12:54:09 +0200
> : Build duration:2 min 35 sec
> :
> : CHANGES
> : No Changes
> :
> : BUILD ARTIFACTS
> : checkout/lucene/build/core/test/temp/junit4-J0-20150619_125429_116.events
> : checkout/lucene/build/core/test/temp/junit4-J1-20150619_125429_116.events
> : checkout/lucene/build/core/test/temp/junit4-J2-20150619_125429_112.events
> : checkout/lucene/build/core/test/temp/junit4-J3-20150619_125429_116.events
> : checkout/lucene/build/core/test/temp/junit4-J4-20150619_125429_112.events
> : checkout/lucene/build/core/test/temp/junit4-J5-20150619_125429_116.events
> : checkout/lucene/build/core/test/temp/junit4-J6-20150619_125429_118.events
> : checkout/lucene/build/core/test/temp/junit4-J7-20150619_125429_119.events
> :
> : FAILED JUNIT TESTS
> : Name: junit.framework Failed: 2 test(s), Passed: 0 test(s), Skipped: 0
> : test(s), Total: 2 test(s)
> : Failed: junit.framework.TestSuite.org.apache.lucene.search.TestNumericRangeQuery32
> : Failed: junit.framework.TestSuite.org.apache.lucene.search.TestNumericRangeQuery32
> : Name: org.apache.lucene.index Failed: 2 test(s), Passed: 774 test(s),
> : Skipped: 23 test(s), Total: 799 test(s)
> : Failed: org.apache.lucene.index.TestIndexWriterExceptions.testAddDocsNonAbortingException
> : Failed: org.apache.lucene.index.TestIndexWriterExceptions.testExceptionFromTokenStream
> :
> : CONSOLE OUTPUT
> : [...truncated 1849 lines...]
> : [junit4] - org.apache.lucene.index.TestIndexWriterExceptions.testExceptionFromTokenStream
> : [junit4] - org.apache.lucene.index.TestIndexWriterExceptions.testAddDocsNonAbortingException
> : [junit4]
> : [junit4]
> : [junit4] JVM J0: 1.02 .. 125.17 = 124.15s
> : [junit4] JVM J1: 1.01 .. 124.41 = 123.39s
> : [junit4] JVM J2: 1.33 .. 124.50 = 123.17s
> : [junit4] JVM J3: 1.11 .. 122.66 = 121.55s
> : [junit4] JVM J4: 1.24 .. 124.04 = 122.80s
> : [junit4] JVM J5: 1.01 .. 127.16 = 126.15s
> : [junit4] JVM J6: 1.00 .. 133.45 = 132.45s
> : [junit4] JVM J7: 1.03 .. 125.12 = 124.08s
> : [junit4] Execution time total: 2 minutes 13 seconds
> : [junit4] Tests summary: 401 suites, 3227 tests, 2 suite-level errors,
> : 2 errors, 48 ignored (44 assumptions)
> : BUILD FAILED
> : /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/build.xml:50:
> : The following error occurred while executing this line:
> : /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/common-build.xml:1444:
> : The following error occurred while executing this line:
> : /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/common-build.xml:999:
> : There were test failures: 401 suites, 3227 tests, 2 suite-level
> : errors, 2 errors, 48 ignored (44 assumptions)
> : Total time: 2 minutes 21 seconds
> :
> : ---------------------------------------------------------------------
> : To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> : For additional commands, e-mail: dev-help@lucene.apache.org
> :
> :
>
> -Hoss
> http://www.lucidworks.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
Re: Any clue why I'm being asked to moderate these messages from
the build system?
Posted by Chris Hostetter <ho...@fucit.org>.
: Clearly they're coming from Elastic......
pretty sure it's just standard moderatation queue stuff...
the first time a (non-subscribed) addr sends an email to the list, it gets
held in the queue -- if the moderator just hits "reply" tothe "accept"
address, then that one message will make it through -- but future messages
will not.
Which is why moderators are encouraged to "reply-all" so that the "allow"
address is also hit -- this ensures that future messages from the same
sender won't get stuck in the moderation queue in the future.
at some point recently elastic changed the email addr used by their CI
system, so it needed to be re-allowed to send mail, and they started
popping back up in the moderation queue.
(As a reminder: questions like this are why we have the moderator list, so
we don't have to distract the entire dev community with meta-discussions
about dealing with moderation)
:
: From: build@elastic.co
: To: dev@elastic.co, dev@lucene.apache.org, simonw@apache.org
: Cc:
: Date: Fri, 19 Jun 2015 10:56:46 +0000
: Subject: [CI] Lucene 5x Linux 64 Test Only - Build # 51986 - Failure!
: BUILD FAILURE
:
: Build URLhttp://build-eu-00.elastic.co/job/lucene_linux_java8_64_test_only/51986/
: Project:lucene_linux_java8_64_test_only
: Randomization:JDKEA9,local,heap[1024m],-server +UseConcMarkSweepGC
: +UseCompressedOops +AggressiveOpts,sec manager on
: Date of build:Fri, 19 Jun 2015 12:54:09 +0200
: Build duration:2 min 35 sec
:
: CHANGES
: No Changes
:
: BUILD ARTIFACTS
: checkout/lucene/build/core/test/temp/junit4-J0-20150619_125429_116.events
: checkout/lucene/build/core/test/temp/junit4-J1-20150619_125429_116.events
: checkout/lucene/build/core/test/temp/junit4-J2-20150619_125429_112.events
: checkout/lucene/build/core/test/temp/junit4-J3-20150619_125429_116.events
: checkout/lucene/build/core/test/temp/junit4-J4-20150619_125429_112.events
: checkout/lucene/build/core/test/temp/junit4-J5-20150619_125429_116.events
: checkout/lucene/build/core/test/temp/junit4-J6-20150619_125429_118.events
: checkout/lucene/build/core/test/temp/junit4-J7-20150619_125429_119.events
:
: FAILED JUNIT TESTS
: Name: junit.framework Failed: 2 test(s), Passed: 0 test(s), Skipped: 0
: test(s), Total: 2 test(s)
: Failed: junit.framework.TestSuite.org.apache.lucene.search.TestNumericRangeQuery32
: Failed: junit.framework.TestSuite.org.apache.lucene.search.TestNumericRangeQuery32
: Name: org.apache.lucene.index Failed: 2 test(s), Passed: 774 test(s),
: Skipped: 23 test(s), Total: 799 test(s)
: Failed: org.apache.lucene.index.TestIndexWriterExceptions.testAddDocsNonAbortingException
: Failed: org.apache.lucene.index.TestIndexWriterExceptions.testExceptionFromTokenStream
:
: CONSOLE OUTPUT
: [...truncated 1849 lines...]
: [junit4] - org.apache.lucene.index.TestIndexWriterExceptions.testExceptionFromTokenStream
: [junit4] - org.apache.lucene.index.TestIndexWriterExceptions.testAddDocsNonAbortingException
: [junit4]
: [junit4]
: [junit4] JVM J0: 1.02 .. 125.17 = 124.15s
: [junit4] JVM J1: 1.01 .. 124.41 = 123.39s
: [junit4] JVM J2: 1.33 .. 124.50 = 123.17s
: [junit4] JVM J3: 1.11 .. 122.66 = 121.55s
: [junit4] JVM J4: 1.24 .. 124.04 = 122.80s
: [junit4] JVM J5: 1.01 .. 127.16 = 126.15s
: [junit4] JVM J6: 1.00 .. 133.45 = 132.45s
: [junit4] JVM J7: 1.03 .. 125.12 = 124.08s
: [junit4] Execution time total: 2 minutes 13 seconds
: [junit4] Tests summary: 401 suites, 3227 tests, 2 suite-level errors,
: 2 errors, 48 ignored (44 assumptions)
: BUILD FAILED
: /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/build.xml:50:
: The following error occurred while executing this line:
: /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/common-build.xml:1444:
: The following error occurred while executing this line:
: /home/jenkins/workspace/lucene_linux_java8_64_test_only/checkout/lucene/common-build.xml:999:
: There were test failures: 401 suites, 3227 tests, 2 suite-level
: errors, 2 errors, 48 ignored (44 assumptions)
: Total time: 2 minutes 21 seconds
:
: ---------------------------------------------------------------------
: To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
: For additional commands, e-mail: dev-help@lucene.apache.org
:
:
-Hoss
http://www.lucidworks.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org