Issue metadata
Sign in to add a comment
|
StrictMode failure landed through CQ then failed on main waterfall |
||||||||||||||||||||||||
Issue descriptionhttps://codereview.chromium.org/1958873002/ landed through the CQ: https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/66811 then failed on the main waterfall w/ a StrictMode failure: https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/34270 https://build.chromium.org/p/chromium.linux/builders/Android%20GN/builds/34198 This shouldn't have landed through the CQ at all.
,
May 9 2016
Looks like it did. Note the number of total & passed tests: https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/66811/steps/chrome_public_test_apk%20%28with%20patch%29%20on%20Android/logs/stdio vs https://build.chromium.org/p/chromium.linux/builders/Android%20Tests%20%28dbg%29/builds/34270/steps/Instrumentation%20test%20chrome_public_test_apk/logs/stdio
,
May 9 2016
I hadn't gotten to checking at the test level but did see that the suite ran. I'm guessing that this is a debug vs release problem w.r.t. StrictMode.
,
May 10 2016
I'll take this if you don't mind.
,
May 10 2016
Sure, go for it.
,
May 10 2016
Patching that CL locally and running the same test on debug (same as Android Tests dbg) cannot reproduce the same error. When I was working with rouslan@ earlier neither of us could reproduce the StrictMode failures on the waterfall bots. :/
,
Jun 6 2016
Embarrassing, but may be fixed by http://crbug.com/615083 , as the sIsDebug flag was always false. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by bpastene@chromium.org
, May 9 2016