bug #637478  is a long-standing open bug that theoretically is tracking webkit_tests hanging when run on Windows.

Unfortunately, it looks like chromium-try-flakes is perhaps incorrectly assigning *all* webkit_tests flakes to it (or at least some of them).

For example, in https://bugs.chromium.org/p/chromium/issues/detail?id=637478#c132 , 29 new flakes are reported. However, 24 of them are actually failures on mac or linux that appear to have been due to r436518 landing without running try jobs (which is "as expected" since it was a re-land).

So, there are several issues here that we should probably split out into separate bugs:

1) these failures are being classified as "flakes" even though there were failures on the waterfall builders at the same time.

2) the failures are being assigned to the "wrong" bug

3) there's no actual way to edit the flakiness assignments in 

https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyJAsSBUZsYWtlIhl3ZWJraXRfdGVzdHMgKHdpdGggcGF0Y2gpDA

to reassociate them with a different bug, or to annotate them that someone has actually triaged the flakes.

I think I've filed bugs related to (1) before. (2) might be a new issue that we could track here. (3) probably deserves a separate bug or bugs on its own.

I'm not sure who the best people to look at this are or what the right components are, but I'm guessing it's estaab and sergiyb, and Infra>Flakiness or Infra>Flakiness>Pipeline :).