Build systems love to fail quietly: one wrong “dependency” edge can trigger compile errors, strange runtime results, or just endless redundant rebuilds that slow every release. Prior research even suggests dependency issues make up a huge share of large build failures—and maintaining build infrastructure can steal a meaningful chunk of developer time. Now Waseda University just open-sourced mkcheck2, a dependency verification tool designed to plug directly into CI workflows. The goal is simple: during a real build, detect missing or extra dependencies and validate them against what your build rules claim—without turning CI into a bottleneck. mkcheck2 builds on an earlier Cambridge idea: trace real file reads/writes during compilation to infer what the program truly depends on, then compare against declared dependencies. The upgrades are the magic: 1) Tracing moved from ptrace to eBPF. Less overhead—measured +148% build time with ptrace vs only ~+0.3% with eBPF. 2) Incremental analysis. Instead of re-checking everything, it analyzes only what changed between builds. On 300 OSS projects, analysis time dropped from 1267.49s to 23.56s (~54× faster). Accuracy: 100% for missing deps, 92% for extra ones. #CI #DevOps #SoftwareEngineering #BuildSystems #DependencyManagement #eBPF
Want to learn more? Visit Explore the world, stay updated on travel insights and international affairs, and discover authentic stories from real life
评论
发表评论