Proguard warning suppresions removed

Proguard warning suppresions removed

Old warning suppressions are kept in proguard.flags file without anyone
caring about them. It seems like removing them has absolutely no effect.

BUG=619937
Committed: https://crrev.com/717861ebc8fd72bcca825c4d5049047a75afd34c
Cr-Commit-Position: refs/heads/master@{#400676}

[smaier, 2016-06-15 19:31:37]

smaier@chromium.org changed reviewers:
+ agrieve@chromium.org, wnwen@chromium.org

[agrieve, 2016-06-16 00:52:52]

The CQ bit was checked by agrieve@chromium.org to run a CQ dry run

[agrieve, 2016-06-16 00:53:00]

On 2016/06/15 19:31:37, smaier wrote:

lgtm

[commit-bot: I haz the power, 2016-06-16 00:53:15]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2069213002/20001

[commit-bot: I haz the power, 2016-06-16 01:18:41]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-06-16 01:18:42]

Dry run: Try jobs failed on following builders:
  linux_android_rel_ng on tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_androi...)

[smaier, 2016-06-16 15:49:42]

The CQ bit was checked by smaier@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-06-16 15:50:23]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2069213002/40001

[commit-bot: I haz the power, 2016-06-16 16:27:18]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-06-16 16:27:19]

Dry run: This issue passed the CQ dry run.

[smaier, 2016-06-20 13:40:34]

The CQ bit was checked by smaier@chromium.org

[smaier, 2016-06-20 13:40:35]

The patchset sent to the CQ was uploaded after l-g-t-m from agrieve@chromium.org
Link to the patchset: https://codereview.chromium.org/2069213002/#ps40001
(title: "Re added org.apache dontwarn")

[commit-bot: I haz the power, 2016-06-20 13:40:52]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2069213002/40001

[commit-bot: I haz the power, 2016-06-20 14:20:17]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-06-20 14:25:11]

Description was changed from

==========
Proguard warning suppresions removed

Old warning suppressions are kept in proguard.flags file without anyone
caring about them. It seems like removing them has absolutely no effect.

BUG=619937
==========

to

==========
Proguard warning suppresions removed

Old warning suppressions are kept in proguard.flags file without anyone
caring about them. It seems like removing them has absolutely no effect.

BUG=619937

Committed: https://crrev.com/717861ebc8fd72bcca825c4d5049047a75afd34c
Cr-Commit-Position: refs/heads/master@{#400676}
==========

[commit-bot: I haz the power, 2016-06-20 14:25:11]

Patchset 3 (id:??) landed as
https://crrev.com/717861ebc8fd72bcca825c4d5049047a75afd34c
Cr-Commit-Position: refs/heads/master@{#400676}

[aelias_OOO_until_Jul13, 2016-06-21 21:41:04]

A revert of this CL (patchset #3 id:40001) has been created in
https://codereview.chromium.org/2084013004/ by aelias@chromium.org.

The reason for reverting is: Reverting on behalf of sheriff, breaks
arm64-builder-rel due to SslCertificate suppression still being needed..

[aelias_OOO_until_Jul13, 2016-06-22 19:06:03]

On 2016/06/21 at 21:41:04, aelias wrote:
> A revert of this CL (patchset #3 id:40001) has been created in
https://codereview.chromium.org/2084013004/ by aelias@chromium.org.
> 
> The reason for reverting is: Reverting on behalf of sheriff, breaks
arm64-builder-rel due to SslCertificate suppression still being needed..

For the record, it wasn't reverted after all because we identified the bot
actually wasn't broken by this patch.

[Ken Rockot(use gerrit already), 2016-06-28 23:14:04]

On 2016/06/22 at 19:06:03, aelias wrote:
> On 2016/06/21 at 21:41:04, aelias wrote:
> > A revert of this CL (patchset #3 id:40001) has been created in
https://codereview.chromium.org/2084013004/ by aelias@chromium.org.
> > 
> > The reason for reverting is: Reverting on behalf of sheriff, breaks
arm64-builder-rel due to SslCertificate suppression still being needed..
> 
> For the record, it wasn't reverted after all because we identified the bot
actually wasn't broken by this patch.

What ended up being the cause of the SslCertificate errors on the builder if not
affected by the suppression? I'm hitting similar errors locally now on a clean
ToT build and therefore cannot build chrome_public_apk.

[agrieve, 2016-06-29 00:34:13]

On 2016/06/28 23:14:04, Ken Rockot wrote:
> On 2016/06/22 at 19:06:03, aelias wrote:
> > On 2016/06/21 at 21:41:04, aelias wrote:
> > > A revert of this CL (patchset #3 id:40001) has been created in
> https://codereview.chromium.org/2084013004/ by mailto:aelias@chromium.org.
> > > 
> > > The reason for reverting is: Reverting on behalf of sheriff, breaks
> arm64-builder-rel due to SslCertificate suppression still being needed..
> > 
> > For the record, it wasn't reverted after all because we identified the bot
> actually wasn't broken by this patch.
> 
> What ended up being the cause of the SslCertificate errors on the builder if
not
> affected by the suppression? I'm hitting similar errors locally now on a clean
> ToT build and therefore cannot build chrome_public_apk.

I think it's still broken in a non-clank checkout due to the recent play
services roll goofing up a bit. Fix is here:
https://codereview.chromium.org/2103193002/.