<feed xmlns='http://www.w3.org/2005/Atom'>
<title>sl0ppij.git/.fastfeedback, branch main</title>
<subtitle>a sl0p.foo repository</subtitle>
<id>https://git.sl0p.foo/sl0ppij.git/atom/.fastfeedback?h=main</id>
<link rel='self' href='https://git.sl0p.foo/sl0ppij.git/atom/.fastfeedback?h=main'/>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/sl0ppij.git/'/>
<updated>2026-08-10T22:12:55Z</updated>
<entry>
<title>sl0p: record the green test baseline in SPEED.md</title>
<updated>2026-08-10T22:12:55Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-08-10T22:12:55Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/sl0ppij.git/commit/?id=5e479cdb056f2fc9e7db303d1b525fc9d20d4ee1'/>
<id>urn:sha1:5e479cdb056f2fc9e7db303d1b525fc9d20d4ee1</id>
<content type='text'>
The tree carried 30 failures in zellij-server and 5 in zellij-utils from the
first sl0p commit until 5f2c28ab. They were never real bugs: aa51848d changed
the scroll indicator and frame-title rendering without refreshing the insta
snapshots. Documents the current green counts so a future context treats any
failure as its own, plus the two traps that hid this for so long -- cargo
stops at the first failing test binary, and insta aborts a test at its first
snapshot mismatch -- and how to regenerate snapshots without cargo-insta.
</content>
</entry>
<entry>
<title>chore: stop tracking transient bgrun job artifacts</title>
<updated>2026-08-08T20:25:18Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-08-08T20:25:18Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/sl0ppij.git/commit/?id=e7bd8f9e9a3e307ce648e14990a629f1881cb036'/>
<id>urn:sha1:e7bd8f9e9a3e307ce648e14990a629f1881cb036</id>
<content type='text'>
A `git add -A` swept in the per-job files bgrun writes beside SPEED.md,
including a 37KB build log, none of which belong in the repo.

SPEED.md stays tracked on purpose: the narrow test commands, measured timings
and the pre-existing test-failure baselines are useful to anyone working on
this fork, not just to an agent.
</content>
</entry>
<entry>
<title>sl0p: add fastdev build profile + SPEED.md (60x faster iteration)</title>
<updated>2026-08-08T18:46:53Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-08-08T18:46:53Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/sl0ppij.git/commit/?id=0d9540e848135ea46531e57c2d16bc28a645230d'/>
<id>urn:sha1:0d9540e848135ea46531e57c2d16bc28a645230d</id>
<content type='text'>
Building this fork for local use took ~3 minutes per one-line change:
[profile.release] sets lto = true and codegen-units = 1, so every rebuild
redid whole-program optimization on a single core. That is right for a
shipped artifact and pure waste for a binary we just want to look at in a
terminal - zellij is bound on a human, not on codegen.

[profile.fastdev] inherits release, keeps opt-level 3, drops LTO, uses 16
codegen units and keeps the incremental cache:

  cargo build --profile fastdev -p zellij   ~2.8s incremental (was ~3min)

[profile.release] is deliberately untouched, so shipping/benchmarking builds
are unchanged.

.fastfeedback/SPEED.md records the narrow commands, measured timings, the
deploy loop, and - importantly - the PRE-EXISTING test failure baselines
(30 in zellij-server, 5 in zellij-utils) so a future session does not waste
time chasing failures it did not cause.

Rejected: the gold linker (rustc warns it is deprecated with known Rust
bugs) and clang+lld (no lld binary installed). Dropping LTO removed the
dominant cost anyway.
</content>
</entry>
</feed>
