Issue 2239763002: Using proper keep rule in testing proguard config

Issue 2239763002: Using proper keep rule in testing proguard config (Closed)

Created:
4 years, 4 months ago by smaier

Modified:
4 years, 4 months ago

Reviewers:
Yaron

CC:
chromium-reviews, jbudorick+watch_chromium.org, mikecase+watch_chromium.org

Base URL:
https://chromium.googlesource.com/chromium/src.git@master

Target Ref:
refs/pending/heads/master

Project:
chromium

Visibility:
Public.

Using proper keep rule in testing proguard config BUG=619937 Committed: https://crrev.com/9e1133795d7be524bb30dcce462016202248c829 Cr-Commit-Position: refs/heads/master@{#411648}

Created: 4 years, 4 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+1 line, -1 line)			Patch
	M	testing/android/proguard_for_test.flags	View		1 chunk	+1 line, -1 line	0 comments	Download

Total messages: 8 (3 generated)

commit-bot: I haz the power

CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2239763002/1

4 years, 4 months ago (2016-08-12 13:44:49 UTC) #5

commit-bot: I haz the power

4 years, 4 months ago (2016-08-12 14:39:06 UTC) #8

Message was sent while issue was closed.

Patchset 1 (id:??) landed as
https://crrev.com/9e1133795d7be524bb30dcce462016202248c829
Cr-Commit-Position: refs/heads/master@{#411648}