It's neither related to Swarming (the task itself didn't time out, a test case did) nor logdog (it doesn't process logs).
I'll assign to Stephen so he can triage.
This theoretically is a problem with gtest logs. I'm pretty sure the recipes just look at the gtest output json and present information from that. I'm trying to verify this, and having a bit of trouble, but I'll look into this.
Showing all of the metadata from the gtest json sounds like it would fix this problem. It has `"status":"TIMEOUT"`, which is exactly what I was missing.
I, as a user, don't know exactly what this log file means today, so you wouldn't be making that any worse, whatever you did. 😃 Putting some markers around the log test might be able to improve it by giving you a place to include explanatory text, delineate the 4 separate test runs that are currently just concatenated, etc.
This is technically done. Not sure if it's the best solution, but I think anything more complicated would need better UI support than buildbot gives us right now.
Comment 1 by jyasskin@chromium.org
, Dec 6