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

Issue 627946 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Backport ARC connectivity CLs to M53

Project Member Reported by cernekee@chromium.org, Jul 13 2016

Issue description

I have a couple of ARC-related CLs that should have landed on 6/30, but did not land until 7/1 due to spurious CQ errors:

https://chromium-review.googlesource.com/#/c/353854/
https://chromium-review.googlesource.com/#/c/357990/
https://chromium-review.googlesource.com/#/c/353743/
https://chromium-review.googlesource.com/#/c/357931/

Consequently they did not make it into the M53 branch (8530.x.y).

The bugs associated with these CLs are in Buganizer only, so I created this ticket to track the merge requests.

 

Comment 1 by snanda@chromium.org, Jul 13 2016

Cc: keta...@chromium.org snanda@chromium.org
+ketakid for M53 merge-approval.
Labels: -Merge-Request-53 Merge-Approved-53 M-53
I think these are all effectively merge-approved through b/, so we should be good to go.
Thanks bhthompson@. Snanda@ let me know if you need anything else. You should be good.

Comment 4 by gov...@chromium.org, Jul 15 2016

Please merge your change to M53 branch 2785 ASAP (latest by 4:00 PM PST on Monday, 07/18) in order to make it to M53 dev release next week before Beta promotion.
Status: Fixed (was: Started)
These are Chrome OS changes and they have been merged into the release-R53-8530.B branch.

Project Member

Comment 6 by sheriffbot@chromium.org, Jul 18 2016

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Merge-Approved-53
Status: Verified (was: Fixed)
Cyan - R53-8530.33.0
android.permission.cts.NoNetworkStatePermissionTest
-- testGetActiveNetworkInfo	pass
-- testGetAllNetworkInfo	pass
-- testGetNetworkInfo	pass
-- testSecurityExceptionFromDns	pass
-- testAndroidTestCaseSetupProperly	pass

- testDnsWorks	fails but as per Issue https://b.corp.google.com/issues/28752805 this must be due to unavailability of IPv6 network. 
junit.framework.AssertionFailedError: [RERUN] ipv6.google.com returned an ipv4 address, check your network's DNS connection.

at junit.framework.Assert.fail(Assert.java:50)

Let me know, if we need to check any other test for verification. 
LGTM, thanks!

Sign in to add a comment