Change typ's interpretation of a test that first fails and is then skipped.

Change typ's interpretation of a test that first fails and is then skipped.

Previously, if a test failed and typ retried it, but for whatever reason
the test was skipped on subsequent retries, the test was considered to
have failed (since it never passed) and so the whole test run failed.

This is perhaps inconsistent with how typ would've reacted if the test
was skipped *every* time, and so arguably this is the wrong thing to do.
For now, I'm changing the behavior so that subsequent skips are treated
like subsequent passes (i.e., the test didn't fail every time).

If you really want different behavior you can look at the full list
of results yourself.

Also, bump the typ version to 0.9.6, and add a codereview.settings flag
so that I can use Rietveld.

R=nednguyen@google.com
BUG=618330

[Dirk Pranke, 2016-07-31 22:59:44]

Description was changed from

==========
Change typ's interpretation of a test that first fails and is then skipped.

Previously, if a test failed and typ retried it, but for whatever reason
the test was skipped on subsequent retries, the test was considered to
have failed (since it never passed) and so the whole test run failed.

This is perhaps inconsistent with how typ would've reacted if the test
was skipped *every* time, and so arguably this is the wrong thing to do.
For now, I'm changing the behavior so that subsequent skips are treated
like subsequent passes (i.e., the test didn't fail every time).

If you really want different behavior you can look at the full list
of results yourself.

Also, bump the typ version to 0.9.6, and add a codereview.settings flag
so that I can use Rietveld.

R=nednguyen@chromium.org
BUG=618330
==========

to

==========
Change typ's interpretation of a test that first fails and is then skipped.

Previously, if a test failed and typ retried it, but for whatever reason
the test was skipped on subsequent retries, the test was considered to
have failed (since it never passed) and so the whole test run failed.

This is perhaps inconsistent with how typ would've reacted if the test
was skipped *every* time, and so arguably this is the wrong thing to do.
For now, I'm changing the behavior so that subsequent skips are treated
like subsequent passes (i.e., the test didn't fail every time).

If you really want different behavior you can look at the full list
of results yourself.

Also, bump the typ version to 0.9.6, and add a codereview.settings flag
so that I can use Rietveld.

R=nednguyen@google.com
BUG=618330
==========

[Dirk Pranke, 2016-07-31 22:59:44]

dpranke@chromium.org changed reviewers:
+ nednguyen@google.com
- nednguyen@chromium.org

[nednguyen, 2016-08-02 21:13:50]

lgtm

[rnephew (Reviews Here), 2016-08-22 20:55:41]

On 2016/08/02 21:13:50, nednguyen wrote:
> lgtm

Any update on landing this? It would be nice to unblacklist the battor tests for
smoke tests. (Done in CL below).

https://codereview.chromium.org/2187183002/

[Dirk Pranke, 2016-08-22 23:14:15]

On 2016/08/22 20:55:41, rnephew (Reviews Here) wrote:
> On 2016/08/02 21:13:50, nednguyen wrote:
> > lgtm
> 
> Any update on landing this? It would be nice to unblacklist the battor tests
for
> smoke tests. (Done in CL below).
> 
> https://codereview.chromium.org/2187183002/

Sorry, I thought you were still trying to fix the other issue.

I can land this in the next day or two.