Comparison
Kogen verification component
Results about how Kogen runs checks and reports failures: timeouts, leftover processes and how precisely a failure is located.
Comparison · site/content/finding-pages.json
Results about how Kogen runs checks and reports failures: timeouts, leftover processes and how precisely a failure is located.
Results, newest first
| Result | Verdict | Finished |
|---|---|---|
| A shaper's probe and the readiness run used different environments | Yes | 7 November 2026 |
| Archiving per-Intent step files leaves the spec trace unchanged, but many of them already name tests that no longer exist | No | 5 November 2026 |
| The replay's Quint batch is fast, but its generator rejects 7 of 17 valid acceptance runs | No | 5 November 2026 |
| On Linux the wall-time deadline test does not fail; its pre-setup work is 4x shorter than on the Mac | Yes | 5 November 2026 |
| The wall-time deadline test starts its clock too early; the loaded run did not happen | Yes | 5 November 2026 |
| Isolated, parallel-safe generated acceptance: no detector with a payoff passes | No | 5 November 2026 |
| A probe copy with git history lets git-reading observers pass | Yes | 5 November 2026 |
| Reaping while the check runs ends the Linux helper's hangs, with no orphans | Yes | 5 November 2026 |
| Linux check helper leaves zombies; reaping while the check runs fixes it in a first run | Unresolved | 5 November 2026 |