Some Extensions API Tests Fail Occassionally |
||||||
Issue description"DnsApiTest.DnsResolveHostname" 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=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyKAsSBUZsYWtlIh1EbnNBcGlUZXN0LkRuc1Jlc29sdmVIb3N0bmFtZQw. 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
,
Jul 27 2016
Issue 632077 has been merged into this issue.
,
Jul 27 2016
Issue 632078 has been merged into this issue.
,
Jul 27 2016
Issue 632060 has been merged into this issue.
,
Jul 27 2016
These tests time out periodically since 7/26. PrinterProviderApiTest.PrintJobWithFileSuccess HidApiTest.HidApp HidApiTest.OnDeviceAdded BluetoothSocketApiTest.Connect PrinterProviderApiTest.PrintJobFailed BluetoothSocketApiTest.Listen DisplaySourceApiTest.DisplaySourceExtension DnsApiTest.DnsResolveHostname PrinterProviderApiTest.PrintJobSuccess HidApiTest.GetUserSelectedDevices PrinterProviderApiTest.NoPrintEventListener HidApiTest.OnDeviceRemoved PrinterProviderApiTest.PrintRequestAppUnloaded PrinterProviderApiTest.PrintRequestDataNotSet DnsApiTest.DnsExtension PrinterProviderApiTest.PrintJobWithFile_FileDeletedBeforeDispatch DnsApiTest.DnsResolveIPLiteral BluetoothSocketApiTest.PermissionDenied PrinterProviderApiTest.PrintRequestInvalidCallbackParam PrinterProviderApiTest.PrintJobAsyncSuccess
,
Jul 27 2016
,
Jul 28 2016
,
Jul 28 2016
It looks like all of these only ever failed on a small handful of bots in semi-quick succession, but not again afterwards. It also looks like they're timing out. I know from my own sheriff rotations that sometimes longer tests just time out occasionally due to various bot conditions, but it's unclear if the test was working and just slow, or if it timed out because we were waiting on a response that never came. I'll keep an eye on these, but it looks as though they're not continuing to flake since the initial batch of bots. +asargent@ also in case this may have been related to revision 91f655b19888da3f86b57ad8c548da93e7b9aba4 (which affects how we set up bindings), and could cause this type of failure - though I would have hoped it would be more deterministic in that case. (Note also that 91f655b19888da3f86b57ad8c548da93e7b9aba4 has since been reverted, but wasn't at the time of these filings.)
,
Sep 23 2016
,
May 15 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by robliao@chromium.org
, Jul 27 2016