ferent now...
- since there are no funds coming from research labs, i am unable to staff
the build system past 2021 (tbh, even this year is a stretch)
- the hardware is far past EOL and literally falling over
- jenkins is, and always will be a PITA to run
shane
--
Shane Knapp
Computer Guy / Voice
we're having some DNS issues here in the EECS department, and our
crack team is working on getting it resolved asap. until then,
jenkins isn't visible to the outside world.
shane
--
Shane Knapp
Computer Guy / Voice of Reason
UC Berkeley EECS Research / RISELab Staff Technical Lead
https
this was resolved by campus IT around 930pm last night.
On Tue, Aug 31, 2021 at 12:54 PM shane knapp ☠ wrote:
>
> we're having some DNS issues here in the EECS department, and our
> crack team is working on getting it resolved asap. until then,
> jenkins isn't visible to the o
aaand we're back!
On Wed, Aug 25, 2021 at 9:24 AM shane knapp ☠ wrote:
> i'll be:
> - upgrading jenkins to the latest LTS
> - moving jenkins to java 11 (from java 8)
> - rebooting everything
>
> sorry for the disruption... there aren't many builds running right now
i'll be:
- upgrading jenkins to the latest LTS
- moving jenkins to java 11 (from java 8)
- rebooting everything
sorry for the disruption... there aren't many builds running right now so
i'll just get this sorted.
shane
--
Shane Knapp
Computer Guy / Voice of Reason
UC Berkeley EECS Research
happy monday!
the server gods did not smile upon us this weekend, and 4 of the workers
are down. we'll most likely need to head to our colo some time today and
give them an in-person kick and see what's going on.
i'll send an update when they're back up.
shane
--
Shane Knapp
Computer Guy
as workers are continuing to fail, i've stopped jenkins from accepting new
builds for the time being.
more updates as they come.
On Mon, Aug 9, 2021 at 9:17 AM shane knapp ☠ wrote:
> happy monday!
>
> the server gods did not smile upon us this weekend, and 4 of the workers
> are
turns out that minikube/k8s and friends were being oom-killed and this was
causing all sorts of weirdnesses.
i've upped the ram limits on all of the k8s jobs to 8G (from 6G), and we'll
keep an eye on things and see how they go.
On Mon, Aug 9, 2021 at 12:02 PM shane knapp ☠ wrote:
> as work
has been
pretty stable, the jenkins administrative GUI is still broken (but at least
i can hack the xml on the bare metal), and we've got 8 workers up and
running.
i'll be sending out another email to this list soon regarding the impending
jenkins 'freeze'.
shane
--
Shane Knapp
Comput
jenkins.
exceptions to this rule include new branches (spark 3.3, i'm looking at
you!), and any major security or critical fixes required for builds.
please let us know if you have any questions!
thanks in advance,
brian & shane
--
Shane Knapp
Computer Guy / Voice of Reason
UC Berkeley EECS Rese
# sysctl stop jenkins
#
goodbye jenkins!
On Mon, Dec 6, 2021 at 12:02 PM shane knapp ☠ wrote:
> hey everyone!
>
> after a marathon run of nearly a decade, we're finally going to be
> shutting down {amp|rise}lab jenkins at the end of this month...
>
> the earliest sna
le Silicon natively, but some 3rd party libraries like
> RocksDB/LevelDB are not ready yet. Since Mac is one of the popular dev
> environments, we are going to keep monitoring and improving gradually for
> Apache Spark 3.3.
>
> Please test Java 17 and let us know your feedback.
>
--
Shane Knapp
Computer Guy / Voice of Reason
UC Berkeley EECS Research / RISELab Staff Technical Lead
https://rise.cs.berkeley.edu
we've been back for about an hour. :)
On Fri, Oct 22, 2021 at 1:52 PM shane knapp ☠ wrote:
> system load on the primary is getting suspiciously high, and free ram has
> mysteriously disappeared and we are rapidly approaching swap. whatever
> could it be?
>
> java.
>
&
created an issue to track stuff:
https://issues.apache.org/jira/browse/SPARK-37571
On Tue, Dec 7, 2021 at 8:25 AM shane knapp ☠ wrote:
> Will you be nuking all the Jenkins-related code in the repo after the 23rd?
>>
>> probably not right away... but soon after jenkins is s
>
> Will you be nuking all the Jenkins-related code in the repo after the 23rd?
>
> probably not right away... but soon after jenkins is shut down. bits of
the docs and spark website will need to be updated as well.
shane
--
Shane Knapp
Computer Guy / Voice of Reason
UC Berkeley E
y'alls can watch
me type the final command:
systemctl stop jenkins
feeling bittersweet,
shane
--
Shane Knapp
Computer Guy / Voice of Reason
UC Berkeley EECS Research / RISELab Staff Technical Lead
https://rise.cs.berkeley.edu
that actually went much faster than anticipated, and we're already back up
and building!
On Thu, Jul 22, 2021 at 10:24 AM shane knapp ☠ wrote:
> i'll be taking jenkins down for a couple of hours today to reboot/clean up
> the workers and finish up the python package installs covered in
&
i'll be taking jenkins down for a couple of hours today to reboot/clean up
the workers and finish up the python package installs covered in
https://github.com/apache/spark/pull/33469/files
shane
--
Shane Knapp
Computer Guy / Voice of Reason
UC Berkeley EECS Research / RISELab Staff Technical
l real-world and research systems. This puts Spark in good company
>>> with some very impressive previous recipients
>>> <https://sigmod.org/sigmod-awards/sigmod-systems-award/>. This award is
>>> really an achievement by the whole community, so I wanted to say congrat
701 - 720 of 720 matches
Mail list logo
