https://findit-for-me.appspot.com/waterfall/flake?key=ag9zfmZpbmRpdC1mb3ItbWVyrwELEhdNYXN0ZXJGbGFrZUFuYWx5c2lzUm9vdCJ5Y2hyb21pdW0ubGludXgvTGludXggVGVzdHMgKGRiZykoMSkoMzIpLzQ1MzU1L3N5bmNfaW50ZWdyYXRpb25fdGVzdHMvVkhkdlEyeHBaVzUwVlhOelUzbHVZMVJsYzNRdVEyOXVabXhwWTNSU1pYTnZiSFYwYVc5dQwLEhNNYXN0ZXJGbGFrZUFuYWx5c2lzGAEM

In this example, the CL caused other major breakages causing the owner to revert. Findit's analysis came back hours later and posted a notification that the CL was identified as the culprit.

Design choice: whether or not still to post notifications to already-reverted CLs. On main waterfall, notifications are posted that Findit confirms the CL as the culprit, however for flaky tests reverts may have been made for other reasons (like in this case).