<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ci on Luther Monson</title>
    <link>https://luth.io/tags/ci/</link>
    <description>Recent content in Ci on Luther Monson</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 18 Sep 2026 20:05:00 -0700</lastBuildDate>
    <atom:link href="https://luth.io/tags/ci/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ePHPm Odds and Ends: OOM-Killed Links, Opcode Scanning, WebSockets and a 44 ms Stall</title>
      <link>https://luth.io/blog/2026/09/ephpm-smaller-angles/</link>
      <pubDate>Fri, 18 Sep 2026 20:05:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/09/ephpm-smaller-angles/</guid>
      <description>&lt;p&gt;Not every fix in &lt;a href=&#34;https://github.com/ephpm/ephpm&#34;&gt;ePHPm&lt;/a&gt; earns a full write-up. A few of the smaller ones have stuck&#xA;with me because the lesson in each was bigger than the diff. Here are four from this summer.&lt;/p&gt;&#xA;&lt;h3 id=&#34;a-release-build-the-oom-killer-kept-eating&#34;&gt;A release build the OOM killer kept eating&lt;/h3&gt;&#xA;&lt;p&gt;ePHPm statically links libphp, ICU and a pile of other C libraries into one Rust binary. It ships for four targets.&#xA;For the v0.4.2 performance release I set the release profile to &lt;code&gt;lto = &amp;quot;fat&amp;quot;&lt;/code&gt; with &lt;code&gt;codegen-units = 1&lt;/code&gt;&#xA;(&lt;a href=&#34;https://github.com/ephpm/ephpm/pull/171&#34;&gt;#171&lt;/a&gt;). Fat LTO pulls every crate&amp;rsquo;s LLVM IR into one module in one process&#xA;and optimizes it as a unit. One codegen unit removes the parallelism that would otherwise spread that memory out.&#xA;That&amp;rsquo;s one very large process at the final link.&lt;/p&gt;</description>
    </item>
    <item>
      <title>shipmates Short Ones: 8 Minutes Extracting Go, and Three Voice-Loop Bugs</title>
      <link>https://luth.io/blog/2026/09/shipmates-short-ones-setup-go-and-voice/</link>
      <pubDate>Sat, 12 Sep 2026 14:35:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/09/shipmates-short-ones-setup-go-and-voice/</guid>
      <description>&lt;p&gt;A few &lt;a href=&#34;https://luth.io/blog/2026/08/shipmates-persona-based-ai-coding-crews/&#34;&gt;shipmates&lt;/a&gt; bugs don&amp;rsquo;t need a whole post each. They were&#xA;too good to leave in commit messages, though.&lt;/p&gt;&#xA;&lt;h3 id=&#34;setup-go-spends-8-minutes-extracting-go-on-windows-ci&#34;&gt;setup-go spends 8 minutes extracting Go on Windows CI&lt;/h3&gt;&#xA;&lt;p&gt;shipmates CI runs on my own &lt;a href=&#34;https://luth.io/blog/2026/08/ephemerd-one-daemon-every-os/&#34;&gt;ephemerd&lt;/a&gt; runners. On Windows those jobs run&#xA;inside a Hyper-V utility VM. The windows-x64 leg kept timing out in &lt;code&gt;actions/setup-go&lt;/code&gt;. Here&amp;rsquo;s the log from&#xA;&lt;a href=&#34;https://github.com/luthermonson/shipmates/pull/48&#34;&gt;PR #48&lt;/a&gt;:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;20:58:46  Setup go version spec 1.26.6&#xA;20:58:46  Attempting to download 1.26.6...     &amp;lt;- tool-cache MISS&#xA;20:58:48  Acquiring 1.26.6 from ...zip&#xA;20:58:53  Extracting Go...&#xA;21:06:46  ERROR: The action &amp;#39;Run actions/setup-go@v5&amp;#39; has timed out after 8 minutes&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Seven seconds from the start of the step to &lt;code&gt;Extracting Go...&lt;/code&gt;. Then almost eight minutes extracting until the step&#xA;timeout killed it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Kata Containers for CI: Boot Cost Isn&#39;t the Problem, File I/O Is</title>
      <link>https://luth.io/blog/2026/09/kata-containers-for-ci/</link>
      <pubDate>Thu, 03 Sep 2026 21:35:00 -0700</pubDate>
      <guid>https://luth.io/blog/2026/09/kata-containers-for-ci/</guid>
      <description>&lt;p&gt;Of the three platforms &lt;a href=&#34;https://luth.io/blog/2026/08/ephemerd-one-daemon-every-os/&#34;&gt;ephemerd&lt;/a&gt; runs jobs on, Linux has the weakest&#xA;isolation. Windows jobs get a Hyper-V isolated container with its own kernel. macOS jobs get a whole VM. A Linux job is&#xA;an ordinary runc container sharing the host kernel. A kernel escape from a Linux job is a host compromise.&#xA;&lt;a href=&#34;https://katacontainers.io/&#34;&gt;Kata Containers&lt;/a&gt; fixes that by putting each container in a lightweight VM with its own&#xA;kernel. It plugs into containerd as just another runtime handler. So I added it in&#xA;&lt;a href=&#34;https://github.com/ephpm/ephemerd/pull/155&#34;&gt;#155&lt;/a&gt;, measured it, and left it off by default. This post is why.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
