Issue metadata
Sign in to add a comment
|
Get network service working fully on Android |
||||||||||||||||||||||
Issue descriptionThis means passing all integration tests (and for features that don't have integration tests). David: assigning to you as an initial owner per conversations.
,
Aug 8
,
Aug 8
,
Sep 4
,
Sep 7
,
Sep 21
,
Oct 26
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e48994eb1dd0750a65ef9e4f6d55195fe8f14c6e commit e48994eb1dd0750a65ef9e4f6d55195fe8f14c6e Author: Clark DuVall <cduvall@chromium.org> Date: Fri Oct 26 18:33:15 2018 Remove passing test from chrome_public_test_apk NS filter TBR=jam@chromium.org Bug: 827531 Change-Id: I1d104ee55e7ff56e62eb30d54301696230ef9784 Reviewed-on: https://chromium-review.googlesource.com/c/1302103 Reviewed-by: Clark DuVall <cduvall@chromium.org> Reviewed-by: John Abd-El-Malek <jam@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#603153} [modify] https://crrev.com/e48994eb1dd0750a65ef9e4f6d55195fe8f14c6e/testing/buildbot/filters/mojo.fyi.network_chrome_public_test_apk.filter
,
Oct 30
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/024b72104d153da4c609c19d09facb8bd48632b6 commit 024b72104d153da4c609c19d09facb8bd48632b6 Author: Clark DuVall <cduvall@chromium.org> Date: Tue Oct 30 18:21:42 2018 Mark AndroidNetworkLibrary as @MainDex When network service runs out of process, it uses a privileged process similar to the GPU process. The network process needs access to AndroidNetworkLibrary, which was not in the main dex. This was causing many failures when running tests with network service turned on on KitKat devices, see example failures: https://ci.chromium.org/p/chromium/builders/luci.chromium.try/android-kitkat-arm-rel/113359 The failures are throwing a ClassNotFoundException for AndroidNetworkLibrary. Bug: 827531 Change-Id: I9003a8469719e06cb5a05482d5b7cf24980a32b0 Reviewed-on: https://chromium-review.googlesource.com/c/1306344 Reviewed-by: agrieve <agrieve@chromium.org> Reviewed-by: Eric Roman <eroman@chromium.org> Reviewed-by: Ted Choc <tedchoc@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#603967} [modify] https://crrev.com/024b72104d153da4c609c19d09facb8bd48632b6/net/android/java/src/org/chromium/net/AndroidNetworkLibrary.java
,
Oct 30
,
Oct 30
,
Dec 7
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/d5b717469103adc677e08318861513d5d37f59dc commit d5b717469103adc677e08318861513d5d37f59dc Author: Clark DuVall <cduvall@chromium.org> Date: Fri Dec 07 22:11:32 2018 Run Android network service APK tests on the main waterfall This runs chrome_public_test_apk and content_shell_test_apk on the phone testers in the main waterfall. We will be going to canary and dev on Android for network service soon, so want to make sure things don't break. For now, not running content_browsertests or components_browsertests for capacity reasons, and these are much less likely to break since they are also covered by the desktop bots. Bug: 827531 Change-Id: I9140bfc3de18f8c29177fa2e92f0129534ea3292 Reviewed-on: https://chromium-review.googlesource.com/c/1355601 Commit-Queue: Clark DuVall <cduvall@chromium.org> Reviewed-by: John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#614841} [modify] https://crrev.com/d5b717469103adc677e08318861513d5d37f59dc/testing/buildbot/chromium.android.fyi.json [modify] https://crrev.com/d5b717469103adc677e08318861513d5d37f59dc/testing/buildbot/chromium.android.json [modify] https://crrev.com/d5b717469103adc677e08318861513d5d37f59dc/testing/buildbot/test_suite_exceptions.pyl [modify] https://crrev.com/d5b717469103adc677e08318861513d5d37f59dc/testing/buildbot/test_suites.pyl
,
Dec 21
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/bb8fc1c99e75f49202c949379d1f5d421d9b7673 commit bb8fc1c99e75f49202c949379d1f5d421d9b7673 Author: Siddhartha <ssid@chromium.org> Date: Fri Dec 21 01:22:37 2018 Fix utility process memory metrics UMA These metrics were recorded, but since they were not part of the xml file, we don't see them on the dashboard. Network team is interested in debugging the memory usage. So, these metrics are important now. BUG=827531 Change-Id: Iaf319fad18e238ca1ddfceb0924955e9036c0d26 Reviewed-on: https://chromium-review.googlesource.com/c/1387387 Commit-Queue: ssid <ssid@chromium.org> Reviewed-by: Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#618424} [modify] https://crrev.com/bb8fc1c99e75f49202c949379d1f5d421d9b7673/tools/metrics/histograms/histograms.xml
,
Jan 17
(5 days ago)
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dxie@chromium.org
, May 29 2018