geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (GEODE-512) unit test suspect string detector needs to provide more info
Date Thu, 29 Oct 2015 23:21:27 GMT


ASF subversion and git services commented on GEODE-512:

Commit fc4bbfc13e3de49d6d217c02dd93662d2d3e01af in incubator-geode's branch refs/heads/feature/GEODE-409
from [~dschneider]
[;h=fc4bbfc ]

GEODE-512: fix unit test suspect string reporter

A couple of problems that have been fixed:
1. If a stack has a "caused by" it will now be included
in the suspect string report.
2. Warning messages were only being partly ignored.
Now they are completely ignored. At some point in the
future we should consider treating a warning message
like error and severe messages.
3. A suspect message can now be up to 128 lines. It used
to be limited to 50 lines.

> unit test suspect string detector needs to provide more info
> ------------------------------------------------------------
>                 Key: GEODE-512
>                 URL:
>             Project: Geode
>          Issue Type: Bug
>          Components: tests
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
> The suspect string detector used by the unit test framework only gives a single line
that is suspect. This makes it hard to fix suspect string tickets.
> Often times the suspect is the beginning of a exception stack. If the entire call stack
was included it would be helpful.
> Also having some context around the suspect string can help. For example what thread
logged the suspect and what happened right before and after the suspect can help.
> Often times the actual logs are no longer available and getting the suspect string to
reproduce can take lots of time.

This message was sent by Atlassian JIRA

View raw message