Skip to main content

Module why

Module why 

Source
Expand description

The report of kizz why: the reasons stored by the most recent build for the tasks under a path, with each step’s untracked /proc and /sys accesses, its connections to the network and to Unix sockets, the system calls it made that the tracer does not know, the recorded machine state of the parts it names, or of every part with --verbose, and how many accesses it ignored.

The tasks under a directory are the task records whose kizz.md is under it; a path that names a file selects the tasks of that file. Among those, the most recent build is the one with the largest build identity, and the report holds the tasks that build ran, each with the step positions of that run. The caller holds the cache lock while it reads, so no build changes the records meanwhile.

Structs§

WhyReport
The report of kizz why for one path.
WhyStep
One step of a task in the report.
WhyTask
One task of the report.

Functions§

why
The report of the most recent build for the tasks under path, an absolute path, read from store.