root-cause-tracing

To trace a runtime error, systematically walk backward through the call stack from the failing operation to locate the initial trigger. This identifies where invalid state or arguments originated, preventing symptom-level fixes.

The best way to find polluting tests is using test bisection. This targeted approach isolates the specific test that prematurely accessed or initialized shared state, revealing the origin of unexpected files or side effects.

To fix deep-stack data origin errors, trace backward through the call chain to locate the original bug trigger. This method targets the true source of invalid data, preventing incorrect fixes and recurring failures.

Add targeted logging and stack capture instrumentation before risky operations. Log the current working directory, arguments, and stack frames to reveal provenance information and clarify unclear data origins during tests.

Use test bisection instead of standard stack trace analysis when debugging test pollution scenarios. Bisection specifically isolates tests that create unexpected files or shared state during CI runs, whereas stack traces show call sequence errors.

This happens when a test accesses or initializes shared state prematurely, creating unexpected files. Trace the failing operation backward through the call chain to identify the exact test trigger and add minimal validation checks.