root-cause-tracing

Root-cause tracing systematically traces errors backward through the call stack to identify the original trigger rather than treating the symptom. Start by instrumenting your code with stack traces and logging at key points, then work upward through the call chain to find where invalid data or incorrect behavior originated.

Use diagnostic bisection to isolate the polluter test. Root-cause tracing provides a script to systematically narrow down which specific test is creating side effects—such as files in wrong locations or git repositories initialized incorrectly—that cascade into failures elsewhere.

Errors manifest deep in execution because invalid state propagates through long call chains. Root-cause tracing traces backward from the symptom to identify the actual source—such as a git init in the wrong directory or database opened with an incorrect path—rather than fixing the downstream manifestation.

Root-cause tracing guides pre-operation logging and stack trace capture across multiple layers. Log state and context before operations execute, then use those traces to connect symptoms back to their original trigger in the execution flow.

Use root-cause tracing when errors recur, symptoms mask the real problem, or debugging time is wasted chasing downstream effects. It's essential for complex systems with long call chains and test pollution where symptom-based fixes don't prevent future failures.

Yes. Root-cause tracing handles scenarios like files created in wrong locations or databases opened with incorrect paths by tracing the call stack backward to find where the invalid path or connection string originated, then fixing it at the source.