You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-dev@jackrabbit.apache.org by Chetan Mehrotra <ch...@gmail.com> on 2017/01/19 09:32:31 UTC

Collect data for test failure in issue itself

It would be helpful while renaming the Hudson created jira issue we
also attach relevant unit-test.log from the module for which test
failed and also record test failure message as comment

This simplifies later analysis as CI only retains reports for past few
builds (not sure on number). For example for some of the older issue
the links to CI are now resulting in 404 (see OAK-5263 for example)

Chetan Mehrotra

Re: Collect data for test failure in issue itself

Posted by Michael Dürig <md...@apache.org>.

Good, point. +1

Michael

On 19.1.17 10:32 , Chetan Mehrotra wrote:
> It would be helpful while renaming the Hudson created jira issue we
> also attach relevant unit-test.log from the module for which test
> failed and also record test failure message as comment
>
> This simplifies later analysis as CI only retains reports for past few
> builds (not sure on number). For example for some of the older issue
> the links to CI are now resulting in 404 (see OAK-5263 for example)
>
> Chetan Mehrotra
>