system_health.memory_mobile:browse:chrome:omnibox is failing on android_webview, but according to (my reading of) expectations.config it should be skipped. Perhaps Go Webview doesn't match Android_Webview? (in which case, how does one disable a failing test on go-webview

Where it appears to be disabled:
https://cs.chromium.org/chromium/src/tools/perf/expectations.config?rcl=c5fb1770298baafa6628a0f743ae049559c39529&l=216


Excerpt from failing run on perf-go-webview-phone #292
https://uberchromegw.corp.google.com/i/internal.client.clank/builders/perf-go-webview-phone/builds/292

...
I    0.031s Main  Output from:
I    0.031s Main  tools/perf/run_benchmark -v --upload-results --browser=android-webview --output-format=chartjson system_health.memory_mobile --output-dir=/tmp/tmpW8mGwL --device=A6R9K17A17901207
I    0.031s Main  ********************************************************************************
Output from run #0:
....
(INFO) 2018-03-07 23:01:04,756 memory_debug._LogProcessInfo:38  127.1 MiB (pid=7639)
[  PASSED  ] 57 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ]  browse:chrome:omnibox@{'case': 'browse', 'group': 'chrome'}
1 FAILED TEST