natsukium/felis
Archived
Watch
1
Code Issues 23 Pull requests Projects Releases 6 Packages Wiki Activity Actions

bench: take kitty 0.49.0 from the locked nixpkgs #381

Merged
natsukium merged 1 commit from bench/kitty-0.49 into main 2026-09-24 19:08:05 +09:00
Conversation 0 Commits 1 Files changed 3 +7 -7
natsukium commented 2026-09-24 19:05:20 +09:00
Owner
Copy link

The published cross-terminal results measured kitty 0.49.0 built from
nixpkgs master and a nixpkgs PR, because nixpkgs-unstable still shipped
0.48.2, so nix develop .#bench could not reproduce the kitty column.
nixpkgs-unstable now carries 0.49.0; bumping both nixpkgs pins (the root
and the dev partition's nixpkgs-dev, kept on one revision) puts it in the
bench shell.

On Linux the new pin yields the same store path as the master build the
run used, so its source row now points at the bench shell. The macOS
row stays: that PR build is a different derivation from the one the
bench shell now provides.

Assisted-by: Claude Code

The published cross-terminal results measured kitty 0.49.0 built from nixpkgs master and a nixpkgs PR, because nixpkgs-unstable still shipped 0.48.2, so `nix develop .#bench` could not reproduce the kitty column. nixpkgs-unstable now carries 0.49.0; bumping both nixpkgs pins (the root and the dev partition's nixpkgs-dev, kept on one revision) puts it in the bench shell. On Linux the new pin yields the same store path as the master build the run used, so its source row now points at the bench shell. The macOS row stays: that PR build is a different derivation from the one the bench shell now provides. Assisted-by: Claude Code
bench: take kitty 0.49.0 from the locked nixpkgs
Some checks failed
bench / Criterion full-suite snapshot (pull_request) Has been skipped
Details
fuzz / cargo fuzz nightly long-run (pull_request) Has been skipped
Details
bench / Criterion regression gate (pull_request) Successful in 2m7s
Details
darwin / detect relevant changes (pull_request) Successful in 4s
Details
darwin / darwin docs-only no-op (pull_request) Has been skipped
Details
darwin / publish felis (aarch64-darwin) (pull_request) Has been skipped
Details
pr / frontend smoke (x86_64-linux) (pull_request) Successful in 1m40s
Details
pr / publish felis (x86_64-linux) (pull_request) Has been skipped
Details
windows / cargo clippy (Windows cross) (pull_request) Successful in 12s
Details
windows / frontend smoke (Windows) (pull_request) Has been cancelled
Details
windows / package felis (x86_64-pc-windows-msvc) (pull_request) Has been cancelled
Details
fuzz / cargo fuzz smoke (per target) (pull_request) Successful in 1m5s
Details
darwin / build felis (aarch64-darwin) (pull_request) Successful in 1m11s
Details
pr / nix flake check (pull_request) Successful in 25s
Details
pr / cargo build / clippy / test / deny (pull_request) Successful in 1m35s
Details
pr / wire schema is compatible with the base (pull_request) Successful in 14s
Details
windows / detect relevant changes (pull_request) Successful in 4s
Details
windows / windows docs-only no-op (pull_request) Has been skipped
Details
windows / cargo nextest (Windows) (pull_request) Successful in 3m54s
Details
26f5d5fd4b
 
The published cross-terminal results measured kitty 0.49.0 built from
nixpkgs master and a nixpkgs PR, because nixpkgs-unstable still shipped
0.48.2, so `nix develop .#bench` could not reproduce the kitty column.
nixpkgs-unstable now carries 0.49.0; bumping both nixpkgs pins (the root
and the dev partition's nixpkgs-dev, kept on one revision) puts it in the
bench shell.

On Linux the new pin yields the same store path as the master build the
run used, so its source row now points at the bench shell. The macOS
row stays: that PR build is a different derivation from the one the
bench shell now provides.

Assisted-by: Claude Code
natsukium deleted branch bench/kitty-0.49 2026-09-24 19:08:05 +09:00
Commenting is not possible because the repository is archived.
Reviewers
No reviewers
Labels
Clear labels   
priority/P0
Must be resolved before the v0.1.0 tag

  
priority/P1
Must be settled before the first public contract freezes

  
priority/P2
Explicitly deferred until after v0.1.0

  
release/v0.1.0
Work tracked for the first tagged release

  
status/blocked
Cannot start now: waits on an upstream release, another issue, or a recorded revisit trigger

  
status/planned
Triaged with a source-grounded plan and a passed pi review; ready to implement

  
type/bug
Shipped behavior that contradicts the docs or the code's own intent; needs a product code change

  
type/design
An open scope or trade-off question; needs a recorded decision in the owning explanation doc before code

  
type/test-gap
Documented or reviewed behavior that no test pins; usually split from a review finding, needs no product code change

  
type/tracker
Parent issue that tracks child work

No labels
priority/P0
priority/P1
priority/P2
release/v0.1.0
status/blocked
status/planned
type/bug
type/design
type/test-gap
type/tracker
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
natsukium/felis!381
No description provided.