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

Issue 876897 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

components_unittests failing on chromium.win/Win7 Tests (dbg)(1)

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Aug 22

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of jonross@chromium.org

components_unittests failing on chromium.win/Win7 Tests (dbg)(1)

Builders failed on: 
- Win7 Tests (dbg)(1): 
  https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win7%20Tests%20%28dbg%29%281%29


 
Cc: sujiezhu@google.com
Owner: manasverma@google.com
Status: Assigned (was: Available)
The error:

[ RUN      ] AutofillMetricsTest.AutofillSuggestionShownTest
../../components/autofill/core/browser/autofill_metrics_unittest.cc(140): error: Value of: entries[i]->metrics
Expected: has 6 elements and there exists some permutation of elements such that:
 - element #0 and (08412363 pointing to "MillisecondsSinceFormParsed", 0) compare metrics ignoring milliseconds since form parsed, and
 - element #1 and (08412347 pointing to "HeuristicType", 51) compare metrics ignoring milliseconds since form parsed, and
 - element #2 and (08412355 pointing to "HtmlFieldType", 0) compare metrics ignoring milliseconds since form parsed, and
 - element #3 and (0841237F pointing to "ServerType", 51) compare metrics ignoring milliseconds since form parsed, and
 - element #4 and (0841232A pointing to "FieldSignature", 540) compare metrics ignoring milliseconds since form parsed, and
 - element #5 and (08412339 pointing to "FormSignature", 356) compare metrics ignoring milliseconds since form parsed
  Actual: { (822617360850595330, 1), (3640361506783159573, 51), (4815584921581567107, 356), (12548035803827306811, 540), (13021611540219886097, 0), (17234680850427059129, 51) }, where the following matchers don't match any elements:
matcher #0: and (08412363 pointing to "MillisecondsSinceFormParsed", 0) compare metrics ignoring milliseconds since form parsed
and where the following elements don't match any matchers:
element #0: (822617360850595330, 1)
Stack trace:
Backtrace:
	StackTraceGetter::CurrentStackTrace [0x036362CA+90]
	testing::internal::UnitTestImpl::CurrentOsStackTraceExceptTop [0x0364C6DA+74]
	testing::internal::AssertHelper::operator= [0x0364C1EB+75]
	autofill::AutofillMetricsTest_LogHiddenRepresentationalFieldSkipDecision_Test::TestBody [0x003DE4A8+5816]
	autofill::AutofillMetricsTest_AutofillSuggestionShownTest_Test::TestBody [0x004204D1+1793]
[  FAILED  ] AutofillMetricsTest.AutofillSuggestionShownTest (94 ms)

Hey masnasverma@ and sujiezhu@,

You've both landed changes in the AutoFill directory recently, with one touching metrics. I've seen this failure appear on Win7 since those patches have landed. It wasn't directly after, so I'm suspecting a flake.

Could you help triage this issue? Thanks!
 Issue 876954  has been merged into this issue.
Labels: -Sheriff-Chromium
I disabled the test in another bug. https://bugs.chromium.org/p/chromium/issues/detail?id=876954

Sign in to add a comment