I’m new to contributing code to open-source projects, and I frequently encounter failing tests with thousands of lines of logs. It’s challenging for me to sift through all that information without feeling overwhelmed and lost. Although I’m not lazy, spending hours reading each line doesn’t seem productive and leaves me clueless. Meanwhile, senior engineers manage to swiftly identify the problem areas in just 10-30 minutes. I feel blind to their methods. Could you recommend a guide for reading failure logs or share tips on how senior engineers do it? Do they skip certain parts or focus on specific keywords? What exactly is their approach?

For example: This is a log I was trying to understand.