Issue metadata
Sign in to add a comment
|
"ForeignFetchRequestHandlerTest.CheckOriginTrialToken_ValidToken" is flaky |
||||||||||||||||||||||||
Issue description"ForeignFetchRequestHandlerTest.CheckOriginTrialToken_ValidToken" is flaky. This issue was created automatically by the chromium-try-flakes app. Please find the right owner to fix the respective test/step and assign this issue to them. If the step/test is infrastructure-related, please add Infra-Troopers label and change issue status to Untriaged. When done, please remove the issue from Sheriff Bug Queue by removing the Sheriff-Chromium label. We have detected 3 recent flakes. List of all flakes can be found at https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNySgsSBUZsYWtlIj9Gb3JlaWduRmV0Y2hSZXF1ZXN0SGFuZGxlclRlc3QuQ2hlY2tPcmlnaW5UcmlhbFRva2VuX1ZhbGlkVG9rZW4M. Flaky tests should be disabled within 30 minutes unless culprit CL is found and reverted. Please see more details here: https://sites.google.com/a/chromium.org/dev/developers/tree-sheriffs/sheriffing-bug-queues#triaging-auto-filed-flakiness-bugs
,
Dec 9 2016
Yeah, this is pretty much the same issue as #672294
,
Dec 9 2016
See https://codereview.chromium.org/2555333006/; I'm updating the TrialTokenValidator functions to take a base::Time, which can probably be used in this case as well.
,
Jul 10 2017
I'm not really working on this, and since this is really the same bug as 672294 it probably makes more sense to merge it into that bug anyway. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by vasi...@chromium.org
, Dec 9 2016Owner: mek@chromium.org
Status: Assigned (was: Untriaged)