<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.10.0">Jekyll</generator><link href="/feed.xml" rel="self" type="application/atom+xml" /><link href="/" rel="alternate" type="text/html" /><updated>2026-02-02T06:43:11+00:00</updated><id>/feed.xml</id><title type="html">OCaml Infrastructure</title><subtitle>WIki to hold the information about the machine resources available to OCaml.org</subtitle><entry><title type="html">Current Bench Maintenance</title><link href="/2024/02/19/current-bench-maintenance.html" rel="alternate" type="text/html" title="Current Bench Maintenance" /><published>2024-02-19T00:00:00+00:00</published><updated>2024-02-19T00:00:00+00:00</updated><id>/2024/02/19/current-bench-maintenance</id><content type="html" xml:base="/2024/02/19/current-bench-maintenance.html"><![CDATA[<p>Due to storage related maintenance operations on Monday 19th February ‘24
between 6:30am and 9:30am (UTC+1), the current-bench benchmarking service will
be unavailable.</p>

<p>Thank you for your patience and understanding during this time.</p>]]></content><author><name></name></author><summary type="html"><![CDATA[Due to storage related maintenance operations on Monday 19th February ‘24 between 6:30am and 9:30am (UTC+1), the current-bench benchmarking service will be unavailable.]]></summary></entry><entry><title type="html">Electrial Work in the Datacentre</title><link href="/2024/01/14/electrical-work.html" rel="alternate" type="text/html" title="Electrial Work in the Datacentre" /><published>2024-01-14T00:00:00+00:00</published><updated>2024-01-14T00:00:00+00:00</updated><id>/2024/01/14/electrical-work</id><content type="html" xml:base="/2024/01/14/electrical-work.html"><![CDATA[<p>There is an electrical shutdown for essential maintenance this weekend, which will affect large parts of the cluster.  All Power9, ARM64, RISC-V, Windows and FreeBSD workers and docs.ci.ocaml.org, docs-data.ocaml.org and the benchmarking servers will be unavailable.  x86_64 workers will be substantially reduced.  Service is expected to resume late on Sunday evening.</p>]]></content><author><name></name></author><summary type="html"><![CDATA[There is an electrical shutdown for essential maintenance this weekend, which will affect large parts of the cluster. All Power9, ARM64, RISC-V, Windows and FreeBSD workers and docs.ci.ocaml.org, docs-data.ocaml.org and the benchmarking servers will be unavailable. x86_64 workers will be substantially reduced. Service is expected to resume late on Sunday evening.]]></summary></entry><entry><title type="html">Relocating opam.ci.ocaml.org and ocaml.ci.dev</title><link href="/2023/12/04/services-moved.html" rel="alternate" type="text/html" title="Relocating opam.ci.ocaml.org and ocaml.ci.dev" /><published>2023-12-04T00:00:00+00:00</published><updated>2023-12-04T00:00:00+00:00</updated><id>/2023/12/04/services-moved</id><content type="html" xml:base="/2023/12/04/services-moved.html"><![CDATA[<p>About six months ago, <a href="https://opam.ci.ocaml.org"><code class="language-plaintext highlighter-rouge">opam-repo-ci</code> (opam.ci.ocaml.org)</a> suffered from a lack of system memory (<a href="https://github.com/ocurrent/opam-repo-ci/issues/220">issue 220</a>) which caused it to be moved to the machine hosting <a href="https://ocaml.ci.dev"><code class="language-plaintext highlighter-rouge">ocaml-ci</code> (ocaml.ci.dev)</a>.</p>

<p>Subsequently, that machine suffered from BTRFS volume corruption (<a href="https://github.com/ocaml/infrastructure/issues/51">issue 51</a>). Therefore, we moved both services to a larger new server. The data was efficiently migrated using BTRFS tools: <code class="language-plaintext highlighter-rouge">btrfs send | btrfs receive</code>.</p>

<p>Since the move, we have seen issues with BTRFS metadata. Plus, we have suffered from a build-up of subvolumes, as reported by other users: <a href="https://github.com/moby/moby/issues/27653">Docker gradually exhausts disk space on BTRFS</a>.</p>

<p>Unfortunately, both services went down on Friday evening (<a href="https://github.com/ocaml/infrastructure/issues/85">issue 85</a>). Analysis showed over 500 BTRFS subvolumes, a shortage of metadata space, and insufficient space to perform a BTRFS <em>rebalance</em>.</p>

<p>Returning to the original configuration of splitting the <code class="language-plaintext highlighter-rouge">ci.dev</code> and OCaml.org services, they have been moved onto new and separate hardware. The underlying filesystem is now a RAID1-backed ext4, formatted with <code class="language-plaintext highlighter-rouge">-i 8192</code> in order to ensure the availability of sufficient inodes. Docker uses Overlayfs. RSYNC was used to copy the databases and logs from the old server. This change should add resilience and has doubled the capacity for storing history logs.</p>]]></content><author><name></name></author><summary type="html"><![CDATA[About six months ago, opam-repo-ci (opam.ci.ocaml.org) suffered from a lack of system memory (issue 220) which caused it to be moved to the machine hosting ocaml-ci (ocaml.ci.dev).]]></summary></entry><entry><title type="html">macOS Sonoma Update</title><link href="/2023/11/09/macos-sonoma.html" rel="alternate" type="text/html" title="macOS Sonoma Update" /><published>2023-11-09T00:00:00+00:00</published><updated>2023-11-09T00:00:00+00:00</updated><id>/2023/11/09/macos-sonoma</id><content type="html" xml:base="/2023/11/09/macos-sonoma.html"><![CDATA[<p><a href="https://github.com/ocurrent/obuilder">OBuilder</a> workers for both Intel and Apple Silicon have been updated from macOS Ventura to <a href="https://www.apple.com/macos/sonoma/">macOS Sonoma</a> 14.1.1.</p>

<p>From today, <a href="https://ocaml.ci.dev">ocaml-ci</a> and <a href="https://opam.ci.ocaml.org">opam-repo-ci</a> will test against Sonoma rather than Ventura.</p>]]></content><author><name></name></author><summary type="html"><![CDATA[OBuilder workers for both Intel and Apple Silicon have been updated from macOS Ventura to macOS Sonoma 14.1.1.]]></summary></entry><entry><title type="html">Current Bench Maintenance</title><link href="/2023/11/06/current-bench-maintenance.html" rel="alternate" type="text/html" title="Current Bench Maintenance" /><published>2023-11-06T00:00:00+00:00</published><updated>2023-11-06T00:00:00+00:00</updated><id>/2023/11/06/current-bench-maintenance</id><content type="html" xml:base="/2023/11/06/current-bench-maintenance.html"><![CDATA[<p>Due to storage related maintenance operations on Wednesday 8th November ‘23 between 12:00pm and 3:00pm (UTC+1), the current-bench benchmarking service will be unavailable.</p>

<p>Thank you for your patience and understanding during this time.</p>]]></content><author><name></name></author><summary type="html"><![CDATA[Due to storage related maintenance operations on Wednesday 8th November ‘23 between 12:00pm and 3:00pm (UTC+1), the current-bench benchmarking service will be unavailable.]]></summary></entry><entry><title type="html">FreeBSD is Available in More Places</title><link href="/2023/09/21/more-freebsd-news.html" rel="alternate" type="text/html" title="FreeBSD is Available in More Places" /><published>2023-09-21T00:00:00+00:00</published><updated>2023-09-21T00:00:00+00:00</updated><id>/2023/09/21/more-freebsd-news</id><content type="html" xml:base="/2023/09/21/more-freebsd-news.html"><![CDATA[<p>Previously the infrastructure team had made FreeBSD available for <a href="https://opam.ci.ocaml.org"><code class="language-plaintext highlighter-rouge">opam-repo-ci</code></a>. 
Now we can announce that the same support has been added to <a href="https://ocaml.ci.dev"><code class="language-plaintext highlighter-rouge">ocaml-ci</code></a>, giving coverage for both OCaml 
4.14 and the new OCaml 5.1 release.  <code class="language-plaintext highlighter-rouge">opam-repo-ci</code> has also been upgraded to support OCaml 5.1. We aim to support both 4.14 as
the Long Term Support release and the latest 5.* release.</p>

<p>Additionally an <a href="http://freebsd-health-check.ocamllabs.io:8080"><code class="language-plaintext highlighter-rouge">opam-health-check</code> instance</a> has been setup to provide 
continuous checking of opam repository packages against FreeBSD 13.2 x86_64 for both the 4.14 and 5.1 releases of OCaml. 
This will allow the community to check whether packages work on FreeBSD and provide fixes to <code class="language-plaintext highlighter-rouge">opam-repository</code> that will 
then get tested on FreeBSD. Closing the loop and giving the community the tools to support OCaml on FreeBSD effectively.</p>

<p>We hope the community finds the FreeBSD support useful.</p>]]></content><author><name></name></author><summary type="html"><![CDATA[Previously the infrastructure team had made FreeBSD available for opam-repo-ci. Now we can announce that the same support has been added to ocaml-ci, giving coverage for both OCaml 4.14 and the new OCaml 5.1 release. opam-repo-ci has also been upgraded to support OCaml 5.1. We aim to support both 4.14 as the Long Term Support release and the latest 5.* release.]]></summary></entry><entry><title type="html">FreeBSD is now tested in opam-repo-ci</title><link href="/2023/08/08/freebsd-testing.html" rel="alternate" type="text/html" title="FreeBSD is now tested in opam-repo-ci" /><published>2023-08-08T00:00:00+00:00</published><updated>2023-08-08T00:00:00+00:00</updated><id>/2023/08/08/freebsd-testing</id><content type="html" xml:base="/2023/08/08/freebsd-testing.html"><![CDATA[<p><a href="https://github.com/ocurrent/obuilder/issues/109">OBuilder</a>
now supports <a href="https://www.freebsd.org">FreeBSD</a> which has allowed
<a href="https://opam.ci.ocaml.org">opam-repo-ci</a> to be extended to test against
it.  Currently, we are testing Opam 2.1.5 with OCaml 4.14.1 and OCaml
5.0 with FreeBSD 13.2 (AMD64).</p>]]></content><author><name></name></author><summary type="html"><![CDATA[OBuilder now supports FreeBSD which has allowed opam-repo-ci to be extended to test against it. Currently, we are testing Opam 2.1.5 with OCaml 4.14.1 and OCaml 5.0 with FreeBSD 13.2 (AMD64).]]></summary></entry><entry><title type="html">Upgrading to Debian 12 for ocaml docker images</title><link href="/2023/06/28/upgrading-linux-distros.html" rel="alternate" type="text/html" title="Upgrading to Debian 12 for ocaml docker images" /><published>2023-06-28T00:00:00+00:00</published><updated>2023-06-28T00:00:00+00:00</updated><id>/2023/06/28/upgrading-linux-distros</id><content type="html" xml:base="/2023/06/28/upgrading-linux-distros.html"><![CDATA[<p>The OCaml infrastructure team is going to move to Debian 12 as the main distribution from Debian 11. We will continue to provide Debian 11 and 10 images while they are supported, dropping Debian 10 when it reaches end of life in 2024-06-30. In addition to these changes we are deprecating Ubuntu 18.04, Alpine 3.16/17, OL7, OpenSuse 15.2 distributions as the have reached end of life. We strongly recommend updating to a newer version if you are still using them.</p>

<p>Please get in touch on https://github.com/ocaml/infrastructure/issues if you have questions or requests for additional support.</p>]]></content><author><name></name></author><summary type="html"><![CDATA[The OCaml infrastructure team is going to move to Debian 12 as the main distribution from Debian 11. We will continue to provide Debian 11 and 10 images while they are supported, dropping Debian 10 when it reaches end of life in 2024-06-30. In addition to these changes we are deprecating Ubuntu 18.04, Alpine 3.16/17, OL7, OpenSuse 15.2 distributions as the have reached end of life. We strongly recommend updating to a newer version if you are still using them.]]></summary></entry><entry><title type="html">Relocation of opam.ci.ocaml.org and ocaml.ci.dev</title><link href="/2023/06/15/opam-repo-ci-ocaml-ci.html" rel="alternate" type="text/html" title="Relocation of opam.ci.ocaml.org and ocaml.ci.dev" /><published>2023-06-15T00:00:00+00:00</published><updated>2023-06-15T00:00:00+00:00</updated><id>/2023/06/15/opam-repo-ci-ocaml-ci</id><content type="html" xml:base="/2023/06/15/opam-repo-ci-ocaml-ci.html"><![CDATA[<p>The server <code class="language-plaintext highlighter-rouge">toxis</code> where <a href="https://opam.ci.ocaml.org">Opam-Repo-CI</a> and <a href="https://ocaml.ci.dev">OCaml-CI</a> were deployed suffered hardware difficulties yesterday, resulting in BTRFS filesystem corruption and memory issues.  These issues are tracked on <a href="https://github.com/ocaml/infrastructure/issues/51">ocaml/infrastructure#51</a>.  Services were restored temporarily using a spare spinning disk, but we continued to see ECC memory issues.</p>

<p>All services have now been redeployed on new ARM64 hardware.  We retained the databases for Prometheus, OCaml-CI and Opam-Repo-CI, but unfortunately, older job logs have been lost.</p>

<p>The external URLs for these services are unchanged.</p>]]></content><author><name></name></author><summary type="html"><![CDATA[The server toxis where Opam-Repo-CI and OCaml-CI were deployed suffered hardware difficulties yesterday, resulting in BTRFS filesystem corruption and memory issues. These issues are tracked on ocaml/infrastructure#51. Services were restored temporarily using a spare spinning disk, but we continued to see ECC memory issues.]]></summary></entry><entry><title type="html">Grafana Dashboard Changes</title><link href="/2023/06/09/grafana-changes.html" rel="alternate" type="text/html" title="Grafana Dashboard Changes" /><published>2023-06-09T00:00:00+00:00</published><updated>2023-06-09T00:00:00+00:00</updated><id>/2023/06/09/grafana-changes</id><content type="html" xml:base="/2023/06/09/grafana-changes.html"><![CDATA[<p>The Grafana dashboards at status.ci3.ocamllabs.io and
status.ci.ocamllabs.io have been merged into a single dashboard at
<a href="https://status.ocaml.ci.dev">status.ci.ocamllabs.io</a>.  HTTP redirects
are in place for the old addresses.</p>]]></content><author><name></name></author><summary type="html"><![CDATA[The Grafana dashboards at status.ci3.ocamllabs.io and status.ci.ocamllabs.io have been merged into a single dashboard at status.ci.ocamllabs.io. HTTP redirects are in place for the old addresses.]]></summary></entry></feed>