Bisecting: Difference between revisions

Mention npc
m Move npc link to a more sensible location
Line 8: Line 8:
* [https://github.com/blitz/hydrasect <code>hydrasect</code>]: select cached commits cached by Hydra
* [https://github.com/blitz/hydrasect <code>hydrasect</code>]: select cached commits cached by Hydra
* [https://github.com/symphorien/nixpkgs-staging-bisecter <code>nixpkgs-staging-bisecter</code>]: reduce number of derivations to be built.
* [https://github.com/symphorien/nixpkgs-staging-bisecter <code>nixpkgs-staging-bisecter</code>]: reduce number of derivations to be built.
* [https://github.com/samestep/npc <code>npc</code>]: bisects Nixpkgs as a flake input (see below), only considering historical channel bumps instead of all <code>master</code> commits.


== Automating bisects ==
== Automating bisects ==
Line 13: Line 14:
* [https://git-scm.com/docs/git-bisect#_bisect_run <code>git bisect run</code>]: runs the selected command until the culprit is found.
* [https://git-scm.com/docs/git-bisect#_bisect_run <code>git bisect run</code>]: runs the selected command until the culprit is found.
* [https://github.com/timokau/nix-bisect <code>nix-bisect</code>]: helps better judge outcome (<code>git bisect</code>'s <code>good</code> vs <code>bad</code> <code>skip</code>) and gives nicer outputs than <code>git bisect run</code>.
* [https://github.com/timokau/nix-bisect <code>nix-bisect</code>]: helps better judge outcome (<code>git bisect</code>'s <code>good</code> vs <code>bad</code> <code>skip</code>) and gives nicer outputs than <code>git bisect run</code>.
* [https://github.com/samestep/npc <code>npc</code>]: bisects Nixpkgs as a flake input (see below), only considering historical channel bumps instead of all <code>master</code> commits.


=== Bisecting dependencies ===
=== Bisecting dependencies ===