Re: yet another jenkins restart early thursday morning -- 730am PDT (and a brief update on our new jenkins infra)

2014-09-11 Thread Josh Rosen 
I purposely disabled the Maven master tests while we’re debugging why they’re 
always failing the Hive tests.  We’ll post an update later when we learn more; 
in the meantime, please don’t trigger those tests, since we don’t want them to 
clobber some of the work that we’re doing by hand in those workspaces.

Thanks,
Josh

On September 11, 2014 at 11:41:38 AM, Matthew Farrellee (m...@redhat.com) wrote:

it was part of the review queue, but it looks like the runs have been  
gc'd. oh well!  

best,  


matt  

On 09/11/2014 12:18 PM, shane knapp wrote:  
> you can just click on 'rebuild', if you'd like. what project  
> specifically? (i had forgotten that i'd killed  
> https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-Maven-with-YARN/557/, 
>  
> which i just started a rebuild on)  
>  
> On Thu, Sep 11, 2014 at 9:15 AM, Matthew Farrellee  > wrote:  
>  
> shane,  
>  
> is there anything we should do for pull requests that failed, but  
> for unrelated issues?  
>  
> best,  
>  
>  
> matt  
>  
> On 09/11/2014 11:29 AM, shane knapp wrote:  
>  
> ...and the restart is done.  
>  
> On Thu, Sep 11, 2014 at 7:38 AM, shane knapp  
> mailto:skn...@berkeley.edu>> wrote:  
>  
> jenkins is now in quiet mode, and a restart is happening soon.  
>  
> On Wed, Sep 10, 2014 at 3:44 PM, shane knapp  
> mailto:skn...@berkeley.edu>> wrote:  
>  
> that's kinda what we're hoping as well. :)  
>  
> On Wed, Sep 10, 2014 at 2:46 PM, Nicholas Chammas <  
> nicholas.cham...@gmail.com  
> > wrote:  
>  
> I'm looking forward to this. :)  
>  
> Looks like Jenkins is having trouble triggering  
> builds for new commits  
> or after user requests (e.g.  
>  >).  
> Hopefully that will be resolved tomorrow.  
>  
> Nick  
>  
> On Tue, Sep 9, 2014 at 5:00 PM, shane knapp  
> mailto:skn...@berkeley.edu>>  
> wrote:  
>  
> since the power incident last thursday, the  
> github pull request builder  
> plugin is still not really working 100%. i  
> found an open issue  
> w/jenkins[1] that could definitely be affecting  
> us, i will be pausing  
> builds early thursday morning and then  
> restarting jenkins.  
> i'll send out a reminder tomorrow, and if this  
> causes any problems for  
> you,  
> please let me know and we can work out a better  
> time.  
>  
> but, now for some good news! yesterday morning,  
> we racked and stacked  
> the  
> systems for the new jenkins instance in the  
> berkeley datacenter.  
> tomorrow  
> i should be able to log in to them and start  
> getting them set up and  
> configured. this is a major step in getting us  
> in to a much more  
> 'production' style environment!  
>  
> anyways: thanks for your patience, and i think  
> we've all learned that  
> hard  
> powering down your build system is a definite  
> recipe for disaster. :)  
>  
> shane  
>  
> [1] --  
> https://issues.jenkins-ci.org/__browse/JENKINS-22509  
>   
>  
>  
>  
>  
>  
>  
>  
>  


-  
To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org  
For additional commands, e-mail: dev-h...@spark.apache.org

Re: yet another jenkins restart early thursday morning -- 730am PDT (and a brief update on our new jenkins infra)

2014-09-11 Thread Matthew Farrellee 
it was part of the review queue, but it looks like the runs have been 
gc'd. oh well!


best,


matt

On 09/11/2014 12:18 PM, shane knapp wrote:

you can just click on 'rebuild', if you'd like.  what project
specifically?  (i had forgotten that i'd killed
https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-Maven-with-YARN/557/,
which i just started a rebuild on)

On Thu, Sep 11, 2014 at 9:15 AM, Matthew Farrellee mailto:m...@redhat.com>> wrote:

shane,

is there anything we should do for pull requests that failed, but
for unrelated issues?

best,


matt

On 09/11/2014 11:29 AM, shane knapp wrote:

...and the restart is done.

On Thu, Sep 11, 2014 at 7:38 AM, shane knapp
mailto:skn...@berkeley.edu>> wrote:

jenkins is now in quiet mode, and a restart is happening soon.

On Wed, Sep 10, 2014 at 3:44 PM, shane knapp
mailto:skn...@berkeley.edu>> wrote:

that's kinda what we're hoping as well.  :)

On Wed, Sep 10, 2014 at 2:46 PM, Nicholas Chammas <
nicholas.cham...@gmail.com
> wrote:

I'm looking forward to this. :)

Looks like Jenkins is having trouble triggering
builds for new commits
or after user requests (e.g.

>).
Hopefully that will be resolved tomorrow.

Nick

On Tue, Sep 9, 2014 at 5:00 PM, shane knapp
mailto:skn...@berkeley.edu>>
wrote:

since the power incident last thursday, the
github pull request builder
plugin is still not really working 100%.  i
found an open issue
w/jenkins[1] that could definitely be affecting
us, i will be pausing
builds early thursday morning and then
restarting jenkins.
i'll send out a reminder tomorrow, and if this
causes any problems for
you,
please let me know and we can work out a better
time.

but, now for some good news!  yesterday morning,
we racked and stacked
the
systems for the new jenkins instance in the
berkeley datacenter.
tomorrow
i should be able to log in to them and start
getting them set up and
configured.  this is a major step in getting us
in to a much more
'production' style environment!

anyways:  thanks for your patience, and i think
we've all learned that
hard
powering down your build system is a definite
recipe for disaster.  :)

shane

[1] --
https://issues.jenkins-ci.org/__browse/JENKINS-22509












-
To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org
For additional commands, e-mail: dev-h...@spark.apache.org

Re: yet another jenkins restart early thursday morning -- 730am PDT (and a brief update on our new jenkins infra)

2014-09-11 Thread shane knapp 
you can just click on 'rebuild', if you'd like.  what project specifically?
 (i had forgotten that i'd killed
https://amplab.cs.berkeley.edu/jenkins/job/Spark-Master-Maven-with-YARN/557/,
which i just started a rebuild on)

On Thu, Sep 11, 2014 at 9:15 AM, Matthew Farrellee  wrote:

> shane,
>
> is there anything we should do for pull requests that failed, but for
> unrelated issues?
>
> best,
>
>
> matt
>
> On 09/11/2014 11:29 AM, shane knapp wrote:
>
>> ...and the restart is done.
>>
>> On Thu, Sep 11, 2014 at 7:38 AM, shane knapp  wrote:
>>
>>  jenkins is now in quiet mode, and a restart is happening soon.
>>>
>>> On Wed, Sep 10, 2014 at 3:44 PM, shane knapp 
>>> wrote:
>>>
>>>  that's kinda what we're hoping as well.  :)

 On Wed, Sep 10, 2014 at 2:46 PM, Nicholas Chammas <
 nicholas.cham...@gmail.com> wrote:

  I'm looking forward to this. :)
>
> Looks like Jenkins is having trouble triggering builds for new commits
> or after user requests (e.g.
> ).
> Hopefully that will be resolved tomorrow.
>
> Nick
>
> On Tue, Sep 9, 2014 at 5:00 PM, shane knapp 
> wrote:
>
>  since the power incident last thursday, the github pull request
>> builder
>> plugin is still not really working 100%.  i found an open issue
>> w/jenkins[1] that could definitely be affecting us, i will be pausing
>> builds early thursday morning and then restarting jenkins.
>> i'll send out a reminder tomorrow, and if this causes any problems for
>> you,
>> please let me know and we can work out a better time.
>>
>> but, now for some good news!  yesterday morning, we racked and stacked
>> the
>> systems for the new jenkins instance in the berkeley datacenter.
>> tomorrow
>> i should be able to log in to them and start getting them set up and
>> configured.  this is a major step in getting us in to a much more
>> 'production' style environment!
>>
>> anyways:  thanks for your patience, and i think we've all learned that
>> hard
>> powering down your build system is a definite recipe for disaster.  :)
>>
>> shane
>>
>> [1] -- https://issues.jenkins-ci.org/browse/JENKINS-22509
>>
>>
>
>

>>>
>>
>

Re: yet another jenkins restart early thursday morning -- 730am PDT (and a brief update on our new jenkins infra)

2014-09-11 Thread Matthew Farrellee 

shane,

is there anything we should do for pull requests that failed, but for 
unrelated issues?


best,


matt

On 09/11/2014 11:29 AM, shane knapp wrote:

...and the restart is done.

On Thu, Sep 11, 2014 at 7:38 AM, shane knapp  wrote:


jenkins is now in quiet mode, and a restart is happening soon.

On Wed, Sep 10, 2014 at 3:44 PM, shane knapp  wrote:


that's kinda what we're hoping as well.  :)

On Wed, Sep 10, 2014 at 2:46 PM, Nicholas Chammas <
nicholas.cham...@gmail.com> wrote:


I'm looking forward to this. :)

Looks like Jenkins is having trouble triggering builds for new commits
or after user requests (e.g.
).
Hopefully that will be resolved tomorrow.

Nick

On Tue, Sep 9, 2014 at 5:00 PM, shane knapp  wrote:


since the power incident last thursday, the github pull request builder
plugin is still not really working 100%.  i found an open issue
w/jenkins[1] that could definitely be affecting us, i will be pausing
builds early thursday morning and then restarting jenkins.
i'll send out a reminder tomorrow, and if this causes any problems for
you,
please let me know and we can work out a better time.

but, now for some good news!  yesterday morning, we racked and stacked
the
systems for the new jenkins instance in the berkeley datacenter.
tomorrow
i should be able to log in to them and start getting them set up and
configured.  this is a major step in getting us in to a much more
'production' style environment!

anyways:  thanks for your patience, and i think we've all learned that
hard
powering down your build system is a definite recipe for disaster.  :)

shane

[1] -- https://issues.jenkins-ci.org/browse/JENKINS-22509













-
To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org
For additional commands, e-mail: dev-h...@spark.apache.org

Re: yet another jenkins restart early thursday morning -- 730am PDT (and a brief update on our new jenkins infra)

2014-09-11 Thread shane knapp 
...and the restart is done.

On Thu, Sep 11, 2014 at 7:38 AM, shane knapp  wrote:

> jenkins is now in quiet mode, and a restart is happening soon.
>
> On Wed, Sep 10, 2014 at 3:44 PM, shane knapp  wrote:
>
>> that's kinda what we're hoping as well.  :)
>>
>> On Wed, Sep 10, 2014 at 2:46 PM, Nicholas Chammas <
>> nicholas.cham...@gmail.com> wrote:
>>
>>> I'm looking forward to this. :)
>>>
>>> Looks like Jenkins is having trouble triggering builds for new commits
>>> or after user requests (e.g.
>>> ).
>>> Hopefully that will be resolved tomorrow.
>>>
>>> Nick
>>>
>>> On Tue, Sep 9, 2014 at 5:00 PM, shane knapp  wrote:
>>>
 since the power incident last thursday, the github pull request builder
 plugin is still not really working 100%.  i found an open issue
 w/jenkins[1] that could definitely be affecting us, i will be pausing
 builds early thursday morning and then restarting jenkins.
 i'll send out a reminder tomorrow, and if this causes any problems for
 you,
 please let me know and we can work out a better time.

 but, now for some good news!  yesterday morning, we racked and stacked
 the
 systems for the new jenkins instance in the berkeley datacenter.
 tomorrow
 i should be able to log in to them and start getting them set up and
 configured.  this is a major step in getting us in to a much more
 'production' style environment!

 anyways:  thanks for your patience, and i think we've all learned that
 hard
 powering down your build system is a definite recipe for disaster.  :)

 shane

 [1] -- https://issues.jenkins-ci.org/browse/JENKINS-22509

>>>
>>>
>>
>

Re: yet another jenkins restart early thursday morning -- 730am PDT (and a brief update on our new jenkins infra)

2014-09-11 Thread shane knapp 
jenkins is now in quiet mode, and a restart is happening soon.

On Wed, Sep 10, 2014 at 3:44 PM, shane knapp  wrote:

> that's kinda what we're hoping as well.  :)
>
> On Wed, Sep 10, 2014 at 2:46 PM, Nicholas Chammas <
> nicholas.cham...@gmail.com> wrote:
>
>> I'm looking forward to this. :)
>>
>> Looks like Jenkins is having trouble triggering builds for new commits or
>> after user requests (e.g.
>> ).
>> Hopefully that will be resolved tomorrow.
>>
>> Nick
>>
>> On Tue, Sep 9, 2014 at 5:00 PM, shane knapp  wrote:
>>
>>> since the power incident last thursday, the github pull request builder
>>> plugin is still not really working 100%.  i found an open issue
>>> w/jenkins[1] that could definitely be affecting us, i will be pausing
>>> builds early thursday morning and then restarting jenkins.
>>> i'll send out a reminder tomorrow, and if this causes any problems for
>>> you,
>>> please let me know and we can work out a better time.
>>>
>>> but, now for some good news!  yesterday morning, we racked and stacked
>>> the
>>> systems for the new jenkins instance in the berkeley datacenter.
>>> tomorrow
>>> i should be able to log in to them and start getting them set up and
>>> configured.  this is a major step in getting us in to a much more
>>> 'production' style environment!
>>>
>>> anyways:  thanks for your patience, and i think we've all learned that
>>> hard
>>> powering down your build system is a definite recipe for disaster.  :)
>>>
>>> shane
>>>
>>> [1] -- https://issues.jenkins-ci.org/browse/JENKINS-22509
>>>
>>
>>
>

Re: yet another jenkins restart early thursday morning -- 730am PDT (and a brief update on our new jenkins infra)

2014-09-10 Thread shane knapp 
that's kinda what we're hoping as well.  :)

On Wed, Sep 10, 2014 at 2:46 PM, Nicholas Chammas <
nicholas.cham...@gmail.com> wrote:

> I'm looking forward to this. :)
>
> Looks like Jenkins is having trouble triggering builds for new commits or
> after user requests (e.g.
> ).
> Hopefully that will be resolved tomorrow.
>
> Nick
>
> On Tue, Sep 9, 2014 at 5:00 PM, shane knapp  wrote:
>
>> since the power incident last thursday, the github pull request builder
>> plugin is still not really working 100%.  i found an open issue
>> w/jenkins[1] that could definitely be affecting us, i will be pausing
>> builds early thursday morning and then restarting jenkins.
>> i'll send out a reminder tomorrow, and if this causes any problems for
>> you,
>> please let me know and we can work out a better time.
>>
>> but, now for some good news!  yesterday morning, we racked and stacked the
>> systems for the new jenkins instance in the berkeley datacenter.  tomorrow
>> i should be able to log in to them and start getting them set up and
>> configured.  this is a major step in getting us in to a much more
>> 'production' style environment!
>>
>> anyways:  thanks for your patience, and i think we've all learned that
>> hard
>> powering down your build system is a definite recipe for disaster.  :)
>>
>> shane
>>
>> [1] -- https://issues.jenkins-ci.org/browse/JENKINS-22509
>>
>
>

Re: yet another jenkins restart early thursday morning -- 730am PDT (and a brief update on our new jenkins infra)

2014-09-10 Thread Nicholas Chammas 
I'm looking forward to this. :)

Looks like Jenkins is having trouble triggering builds for new commits or
after user requests (e.g.
).
Hopefully that will be resolved tomorrow.

Nick

On Tue, Sep 9, 2014 at 5:00 PM, shane knapp  wrote:

> since the power incident last thursday, the github pull request builder
> plugin is still not really working 100%.  i found an open issue
> w/jenkins[1] that could definitely be affecting us, i will be pausing
> builds early thursday morning and then restarting jenkins.
> i'll send out a reminder tomorrow, and if this causes any problems for you,
> please let me know and we can work out a better time.
>
> but, now for some good news!  yesterday morning, we racked and stacked the
> systems for the new jenkins instance in the berkeley datacenter.  tomorrow
> i should be able to log in to them and start getting them set up and
> configured.  this is a major step in getting us in to a much more
> 'production' style environment!
>
> anyways:  thanks for your patience, and i think we've all learned that hard
> powering down your build system is a definite recipe for disaster.  :)
>
> shane
>
> [1] -- https://issues.jenkins-ci.org/browse/JENKINS-22509
>

yet another jenkins restart early thursday morning -- 730am PDT (and a brief update on our new jenkins infra)

2014-09-09 Thread shane knapp 
since the power incident last thursday, the github pull request builder
plugin is still not really working 100%.  i found an open issue
w/jenkins[1] that could definitely be affecting us, i will be pausing
builds early thursday morning and then restarting jenkins.
i'll send out a reminder tomorrow, and if this causes any problems for you,
please let me know and we can work out a better time.

but, now for some good news!  yesterday morning, we racked and stacked the
systems for the new jenkins instance in the berkeley datacenter.  tomorrow
i should be able to log in to them and start getting them set up and
configured.  this is a major step in getting us in to a much more
'production' style environment!

anyways:  thanks for your patience, and i think we've all learned that hard
powering down your build system is a definite recipe for disaster.  :)

shane

[1] -- https://issues.jenkins-ci.org/browse/JENKINS-22509