Remove fixed tests from TestExpectation file

Remove fixed tests from TestExpectation file

These tests were failing because of a state that was
not reset in the content_shell and it was being carried
over from other tests and resulting these test to fail.
The blocking bug is now fixed and that state is being
reset so these tests are always passing now.

Marking the rest of the tests for another bug as they seem to have another reason for failing.

BUG=591821, 594672
Committed: https://crrev.com/228ea6faf71a8e33938caf6d2c04f80ae786dbf2
Cr-Commit-Position: refs/heads/master@{#381211}

[Navid Zolghadr, 2016-03-14 14:52:53]

Description was changed from

==========
Remove fixed tests from TestExpectation file

These tests were failing because of a state that was
not reset in the content_shell and it was being carried
over from other tests and resulting these test to fail.
The blocking bug is now fixed and that state is being
reset so these tests are always passing now.

BUG=59182
==========

to

==========
Remove fixed tests from TestExpectation file

These tests were failing because of a state that was
not reset in the content_shell and it was being carried
over from other tests and resulting these test to fail.
The blocking bug is now fixed and that state is being
reset so these tests are always passing now.

BUG=591821
==========

[Navid Zolghadr, 2016-03-14 15:28:29]

nzolghadr@chromium.org changed reviewers:
+ mustaq@chromium.org, rbyers@chromium.org

[mustaq, 2016-03-14 15:45:34]

On 2016/03/14 15:28:29, Navid Zolghadr wrote:

Thanks Navid for the investigation that led to this cleanup.

There are 13 more entries in the TestExpectations file that were not mentioned
in the bug. If they (or some of them) keep failing, please file a separate bug
for them.

LGTM otherwise.

[Rick Byers, 2016-03-14 19:13:07]

On 2016/03/14 15:45:34, mustaq wrote:
> On 2016/03/14 15:28:29, Navid Zolghadr wrote:
> 
> Thanks Navid for the investigation that led to this cleanup.
> 
> There are 13 more entries in the TestExpectations file that were not mentioned
> in the bug. If they (or some of them) keep failing, please file a separate bug
> for them.
> 
> LGTM otherwise.

Yep this is great, thank you!

Note that you don't need my stamp - everyone is an OWNER in LayoutTests

[Navid Zolghadr, 2016-03-14 20:25:53]

Description was changed from

==========
Remove fixed tests from TestExpectation file

These tests were failing because of a state that was
not reset in the content_shell and it was being carried
over from other tests and resulting these test to fail.
The blocking bug is now fixed and that state is being
reset so these tests are always passing now.

BUG=591821
==========

to

==========
Remove fixed tests from TestExpectation file

These tests were failing because of a state that was
not reset in the content_shell and it was being carried
over from other tests and resulting these test to fail.
The blocking bug is now fixed and that state is being
reset so these tests are always passing now.

BUG=591821, 594672
==========

[Navid Zolghadr, 2016-03-14 20:26:28]

Description was changed from

==========
Remove fixed tests from TestExpectation file

These tests were failing because of a state that was
not reset in the content_shell and it was being carried
over from other tests and resulting these test to fail.
The blocking bug is now fixed and that state is being
reset so these tests are always passing now.

BUG=591821, 594672
==========

to

==========
Remove fixed tests from TestExpectation file

These tests were failing because of a state that was
not reset in the content_shell and it was being carried
over from other tests and resulting these test to fail.
The blocking bug is now fixed and that state is being
reset so these tests are always passing now.

Marking the rest of the tests for another bug as they seem to have another
reason for failing.

BUG=591821, 594672
==========

[Navid Zolghadr, 2016-03-15 12:10:22]

The CQ bit was checked by nzolghadr@chromium.org

[Navid Zolghadr, 2016-03-15 12:10:22]

The patchset sent to the CQ was uploaded after l-g-t-m from mustaq@chromium.org
Link to the patchset: https://codereview.chromium.org/1798963003/#ps40001
(title: " ")

[commit-bot: I haz the power, 2016-03-15 12:10:26]

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

[commit-bot: I haz the power, 2016-03-15 12:15:04]

Description was changed from

==========
Remove fixed tests from TestExpectation file

These tests were failing because of a state that was
not reset in the content_shell and it was being carried
over from other tests and resulting these test to fail.
The blocking bug is now fixed and that state is being
reset so these tests are always passing now.

Marking the rest of the tests for another bug as they seem to have another
reason for failing.

BUG=591821, 594672
==========

to

==========
Remove fixed tests from TestExpectation file

These tests were failing because of a state that was
not reset in the content_shell and it was being carried
over from other tests and resulting these test to fail.
The blocking bug is now fixed and that state is being
reset so these tests are always passing now.

Marking the rest of the tests for another bug as they seem to have another
reason for failing.

BUG=591821, 594672
==========

[commit-bot: I haz the power, 2016-03-15 12:15:05]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-03-15 12:18:24]

Description was changed from

==========
Remove fixed tests from TestExpectation file

These tests were failing because of a state that was
not reset in the content_shell and it was being carried
over from other tests and resulting these test to fail.
The blocking bug is now fixed and that state is being
reset so these tests are always passing now.

Marking the rest of the tests for another bug as they seem to have another
reason for failing.

BUG=591821, 594672
==========

to

==========
Remove fixed tests from TestExpectation file

These tests were failing because of a state that was
not reset in the content_shell and it was being carried
over from other tests and resulting these test to fail.
The blocking bug is now fixed and that state is being
reset so these tests are always passing now.

Marking the rest of the tests for another bug as they seem to have another
reason for failing.

BUG=591821, 594672

Committed: https://crrev.com/228ea6faf71a8e33938caf6d2c04f80ae786dbf2
Cr-Commit-Position: refs/heads/master@{#381211}
==========

[commit-bot: I haz the power, 2016-03-15 12:18:25]

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