New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 873658 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: ----



Sign in to add a comment

Findit should provide more support to reproduce an issue locally.

Project Member Reported by ahaas@google.com, Aug 13

Issue description

Findit recently reported that a CL of mine caused a flake in a layout test, see https://bugs.chromium.org/p/chromium/issues/detail?id=870187. Thank you very much for that. However, I think it is unnecessarily hard to investigate the issue. Would it be possible that Findit provides essential debugging information, like the gn args to compile locally, and the command to execute the failing test? This information is already available in V8, see https://logs.chromium.org/logs/v8/buildbucket/cr-buildbucket.appspot.com/8938307409287814416/+/steps/Check/0/logs/module-memory/0, and it is very helpful and helps to avoid lots of frustration.

If this kind of support is already provided, then I did not find it. Could it be made more visible?

I managed to use swarming.py to reproduce the issue locally, but I don't know what I should do with this information. How can I check if a new CL fixes the issue?

Thanks
 

Sign in to add a comment