system_health.memory_mobile.reference failing on 4 Android builders |
||||
Issue descriptionsystem_health.memory_mobile.reference failing on 4 builders Type: build-failure Builders failed on: - Android Nexus5 Perf (1): https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus5%20Perf%20%281%29 - Android Nexus6 Perf (1): https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus6%20Perf%20%281%29 - Android Nexus9 Perf (1): https://build.chromium.org/p/chromium.perf/builders/Android%20Nexus9%20Perf%20%281%29 - Android One Perf (1): https://build.chromium.org/p/chromium.perf/builders/Android%20One%20Perf%20%281%29
,
Jan 25 2017
Hmhh, I thought we were able to ignore the return code on reference build?
,
Jan 25 2017
Is that documented somewhere? I disagree with the premise, we should not leave a failing test regardless of wether it is a reference or not on the waterfall, but this might not be the best place to discuss that.
,
Jan 25 2017
After an offline discussion, it seems that 1 failing story out of 20 for reference build is not a big factor, and the other 19 provide valuable reference data. Therefore I withdrew my objection. But I think we should be able to track the failing cases in another way.
,
Jan 25 2017
,
Feb 23 2017
This benchmark is still failing on Android bots. https://luci-logdog.appspot.com/v/?s=chrome%2Fbb%2Fchromium.perf%2FAndroid_Nexus5_Perf__1_%2F5288%2F%2B%2Frecipes%2Fsteps%2Fsystem_health.memory_mobile.reference%2F0%2Fstdout Any update on this?
,
Mar 29 2017
failing reference builds no longer turn android bots red. Should this be marked as Fixed/WontFix?
,
Mar 29 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by fmea...@chromium.org
, Jan 24 2017