The OCaml Planet RSS

day10 now runs side-by-side with OBuilder on the RISC-V opam-repo-ci workers, and the layer cache shows why it wins. Plus the Lwt bug that stopped Windows workers reconnecting to the scheduler, an LTSC 2022 image that hadn’t built in months, and ocaml.org taken down by a 371 MB search index.

Correcting last week’s opam-repo-ci overlay, running day10 alongside OBuilder on every job, and fixing the Windows sparse-file error at its source. Plus Tessera tiles dispatched in Zarr order, and a C11 compiler written by Claude Fable that builds OCaml.

Finally, a benchmark that compares day10 with obuilder, making day10 die cleanly and porting opam-repo-ci. Plus Tessera MODIS results showing reduced temporal stability.

Testing day10 on the RISC-V path in OCaml-CI, diagnosing failed Windows containerd commits, and measuring the Tessera / Microsoft Planetary Computer download bottleneck.

This week, six million Tessera S3 objects were renamed. ocaml-gdal was extended to handle vector formats. FreeBSD CI performance investigations and OCaml compiler updates. Further work on day10 and OCaml CI.

Git 2.55 broke opam repo add for all the 4.x base images, and ocaml.org was under scraper attack. On the Tessera side, the v1 dataset got converted to Zarr via Fargate, and there was further investigation into the banding correction.

A big week, with a couple of long-running efforts finally wrapping up: the Source Cooperative mirror is essentially complete now that we have direct write access, and the three-week Ceph resize has converged. Elsewhere, a slow-down in the genesis job server that looked like a garbage-collector problem turned out to be an HTTP handling bug.

The main threads: making day10 a native OCluster job type, porting opam-health-check to use day10, keeping the CI dashboards ahead of both a scraper farm and the opam 2.6 alpha, and a lot of Tessera. New v2 “student” models, the v1.1 mirror to Source Cooperative continues, and diagonal banding in the Amazon mosaic.

I was on holiday for most of week 29, so just a few high-priority issues to report on.

The week 26 summary worked well, so I’m doing it again. This is really a nine-day week as the last weekly post was on 26 June.