geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anthony Baker (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-512) unit test suspect string detector needs to provide more info
Date Fri, 08 Jan 2016 04:40:46 GMT

     [ https://issues.apache.org/jira/browse/GEODE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anthony Baker updated GEODE-512:
--------------------------------
    Fix Version/s: 1.0.0-alpha1

> unit test suspect string detector needs to provide more info
> ------------------------------------------------------------
>
>                 Key: GEODE-512
>                 URL: https://issues.apache.org/jira/browse/GEODE-512
>             Project: Geode
>          Issue Type: Bug
>          Components: tests
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>             Fix For: 1.0.0-alpha1
>
>
> 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
(v6.3.4#6332)

Mime
View raw message