we're back and building!
On Tue, May 4, 2021 at 4:03 PM shane knapp ☠ wrote:
> jenkins went down some time in the past few days, and i'm currently
> investigating.
>
> if it's been down a while, i apologize as i've been dealing w/some health
> issues.
>
> shane
> --
> Shane Knapp
> Computer Guy
jenkins went down some time in the past few days, and i'm currently
investigating.
if it's been down a while, i apologize as i've been dealing w/some health
issues.
shane
--
Shane Knapp
Computer Guy / Voice of Reason
UC Berkeley EECS Research / RISELab Staff Technical Lead
https://rise.cs.berkel
@Cheng Lian just recreated the Jenkins service. The
service is up now.
Thank you for your patience,
Xiao
Dongjoon Hyun 于2020年1月24日周五 上午10:32写道：
> Thank you for updating!
>
> On Fri, Jan 24, 2020 at 10:29 AM Xiao Li wrote:
>
>> It does not block any Spark release. Reduced the priority to Crit
Thank you for updating!
On Fri, Jan 24, 2020 at 10:29 AM Xiao Li wrote:
> It does not block any Spark release. Reduced the priority to Critical.
>
> Cheers,
>
> Xiao
>
> Dongjoon Hyun 于2020年1月24日周五 上午10:24写道：
>
>> Thank you for working on that, Xiao.
>>
>> BTW, I'm wondering why SPARK-30636 is
It does not block any Spark release. Reduced the priority to Critical.
Cheers,
Xiao
Dongjoon Hyun 于2020年1月24日周五 上午10:24写道：
> Thank you for working on that, Xiao.
>
> BTW, I'm wondering why SPARK-30636 is a blocker for 2.4.5 release?
>
> Do you mean `Critical`?
>
> Bests,
> Dongjoon.
>
> On Fri
Thank you for working on that, Xiao.
BTW, I'm wondering why SPARK-30636 is a blocker for 2.4.5 release?
Do you mean `Critical`?
Bests,
Dongjoon.
On Fri, Jan 24, 2020 at 10:20 AM Xiao Li wrote:
> Hi, all,
>
> Because the Jenkins of spark-packages.org is down, new packages or
> releases are una
Hi, all,
Because the Jenkins of spark-packages.org is down, new packages or releases
are unable to be created in spark-packages.org.
Now, we are working on it. For the latest status, please follow the ticket
https://issues.apache.org/jira/browse/SPARK-30636.
Happy lunar new year,
Xiao
our colo is performing some electrical work next week, and jenkins
will be down between 630-930am PST.
sorry for the interruption in service... i'll be following up on this
thread w/updates as they come in.
--
Shane Knapp
Computer Guy / Voice of Reason
UC Berkeley EECS Research / RISELab Staff T
for running k8s tests locally, i have a section dedicated to that here:
https://spark.apache.org/developer-tools.html
minikube and friends is pretty straightforward to set up, but we're
running an older version of the former. i am planning on addressing
that (and moving us to a recent release) by
yeah, as long as tests are run locally i'm ok w/merging. once
california is elevated from 'developing country' status to 'holy crap,
the magic of electricity has returned!' and we can automatically build
again any errors that slipped through will be caught in jenkins.
this means we'll need to kee
On Thu, Oct 10, 2019 at 9:13 AM Xiao Li wrote:
> Thanks! Shane!
>
> AFAIK, it normally takes *more than 5/6 hours* to run all the tests. Any
> major changes in Core/SQL require running all the tests. If any committer
> did it before merging the code, I think it is fine to merge it.
>
Glad were on
Thanks! Shane!
AFAIK, it normally takes *more than 5/6 hours* to run all the tests. Any
major changes in Core/SQL require running all the tests. If any committer
did it before merging the code, I think it is fine to merge it.
Xiao
Holden Karau 于2019年10月10日周四 上午9:11写道：
> Awesome, thanks Shane :
Awesome, thanks Shane :)
In the meantime I think committers can just run tests locally and it’ll be
a slower process but I don’t think we need to halt all merging.
On Thu, Oct 10, 2019 at 9:07 AM Shane Knapp wrote:
> if we do get power back before the weekend, i can have my sysadmin
> head down
if we do get power back before the weekend, i can have my sysadmin
head down to the colo friday afternoon and power up jenkins. he knows
the drill.
On Thu, Oct 10, 2019 at 8:50 AM Holden Karau wrote:
>
> I think a reasonable, albeit slow, option is to run the tests locally. Since
> the outage
I think a reasonable, albeit slow, option is to run the tests locally.
Since the outage could be as long as five days I’d rather not just have PRs
pile up for that entire period.
On Thu, Oct 10, 2019 at 8:38 AM Xiao Li wrote:
> I think we are unable to merge any major PR if we do not know whethe
Please check the note from Shane.
[build system] IMPORTANT! northern california fire danger, potential power
outage(s)
Thomas graves 于2019年10月10日周四 上午8:35写道：
> This is directed towards committers/PMC members.
>
> It looks like Jenkins will be down for a while, what is everyone's
> thoughts on c
I think we are unable to merge any major PR if we do not know whether the
tests can pass.
Xiao
Xiao Li 于2019年10月10日周四 上午8:36写道：
> Please check the note from Shane.
>
> [build system] IMPORTANT! northern california fire danger, potential power
> outage(s)
>
> Thomas graves 于2019年10月10日周四 上午8:35
This is directed towards committers/PMC members.
It looks like Jenkins will be down for a while, what is everyone's
thoughts on committing PRs while its down? Do we want to wait for
Jenkins to come back up, manually run things ourselves and commit?
Tom
--
Thanks, Shane!
On Mon, Nov 19, 2018 at 12:15 PM Marco Gaido wrote:
> Thanks Shane!
>
> Il giorno lun 19 nov 2018 alle ore 19:14 shane knapp
> ha scritto:
>
>> alright, we're back and building.
>>
>> On Mon, Nov 19, 2018 at 10:11 AM shane knapp wrote:
>>
>>> thanks for the heads up... looks li
Thanks Shane!
Il giorno lun 19 nov 2018 alle ore 19:14 shane knapp
ha scritto:
> alright, we're back and building.
>
> On Mon, Nov 19, 2018 at 10:11 AM shane knapp wrote:
>
>> thanks for the heads up... looks like the backup process got wedged.
>> i'll restart jenkins now.
>>
>> On Mon, Nov 19
alright, we're back and building.
On Mon, Nov 19, 2018 at 10:11 AM shane knapp wrote:
> thanks for the heads up... looks like the backup process got wedged.
> i'll restart jenkins now.
>
> On Mon, Nov 19, 2018 at 9:56 AM Sean Owen wrote:
>
>> Jenkins says it's shutting down; I assume shane nee
thanks for the heads up... looks like the backup process got wedged. i'll
restart jenkins now.
On Mon, Nov 19, 2018 at 9:56 AM Sean Owen wrote:
> Jenkins says it's shutting down; I assume shane needs to cycle it.
> Note also that the Apache - github sync looks like it is stuck;
> nothing has s
Jenkins says it's shutting down; I assume shane needs to cycle it.
Note also that the Apache - github sync looks like it is stuck;
nothing has synced since yesterday:
https://github.com/apache/spark/commits/master
That might also be a factor in whatever you're observing.
On Mon, Nov 19, 2018 at 10:
Hi all,
I see that Jenkins is not starting builds for the PRs today. Is it in
maintenance?
Thanks,
Marco
thanks everyone! happy friday! :)
On Fri, Apr 24, 2015 at 3:37 PM, York, Brennon
wrote:
> Ditto to Reynold. Thanks a bunch for all the updates and work Shane!
>
> On 4/24/15, 3:25 PM, "Reynold Xin" wrote:
>
> >Thanks for looking into this, Shane.
> >
> >On Fri, Apr 24, 2015 at 3:18 PM, shane
Ditto to Reynold. Thanks a bunch for all the updates and work Shane!
On 4/24/15, 3:25 PM, "Reynold Xin" wrote:
>Thanks for looking into this, Shane.
>
>On Fri, Apr 24, 2015 at 3:18 PM, shane knapp wrote:
>
>> ok, jenkins is back up and building. we have a few things to mop up
>>here
>> (gangli
Thanks for looking into this, Shane.
On Fri, Apr 24, 2015 at 3:18 PM, shane knapp wrote:
> ok, jenkins is back up and building. we have a few things to mop up here
> (ganglia is sad), but i think we'll be good for the afternoon.
>
> shane
>
> On Fri, Apr 24, 2015 at 2:17 PM, shane knapp wrote:
ok, jenkins is back up and building. we have a few things to mop up here
(ganglia is sad), but i think we'll be good for the afternoon.
shane
On Fri, Apr 24, 2015 at 2:17 PM, shane knapp wrote:
> ok, power has been restored and jenkins is back up. we might be taking
> things down again to fix
ok, power has been restored and jenkins is back up. we might be taking
things down again to fix up some power mis-cabling (jon and i are in the
colo, and the jenkins master wasn't on the UPS and needs to be).
more updates as they come. sorry for the inconvenience.
On Fri, Apr 24, 2015 at 11:33
looks like we had a power failure on campus, and our datacenter is working
to bring things back up:
http://systemstatus.berkeley.edu/
On Fri, Apr 24, 2015 at 11:24 AM, shane knapp wrote:
> jenkins is currently unreachable. i'm not entirely sure why, as i can't
> ssh in to the box and see what'
jenkins is currently unreachable. i'm not entirely sure why, as i can't
ssh in to the box and see what's going on. i've filed a ticket and will
let everyone know when i have more information.
shane
ok, we're back up and building now... looks like there was a seriously bad
git (or github) plugin update that caused all sorts of unintended
consequences, mostly with cron stacktracing.
i'll take a closer look and see if i can find out exactly what happened,
but suffice to say, we'll be really ca
i noticed that there were no builds, and noticed that it's throwing a bunch
of exceptions in the log file.
i'm looking in to this right now and will update when i get things rolling
again.
sorry for the inconvenience,
shane
33 matches
Mail list logo
