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

Posted to notifications@yetus.apache.org by "Yetus QA (JIRA)" <ji...@apache.org> on 2019/03/01 07:11:00 UTC

[jira] [Commented] (YETUS-679) dupname should report even in case of sucess

    [ https://issues.apache.org/jira/browse/YETUS-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781363#comment-16781363 ] 

Yetus QA commented on YETUS-679:
--------------------------------

(!) A patch to the testing environment has been detected. 
Re-executing against the patched versions to perform further tests. 
The console is at https://builds.apache.org/job/PreCommit-YETUS-Build/954/console in case of problems.


> dupname should report even in case of sucess
> --------------------------------------------
>
>                 Key: YETUS-679
>                 URL: https://issues.apache.org/jira/browse/YETUS-679
>             Project: Yetus
>          Issue Type: New Feature
>          Components: Test Patch
>    Affects Versions: 0.8.0
>            Reporter: Allen Wittenauer
>            Assignee: Allen Wittenauer
>            Priority: Major
>              Labels: beginner
>             Fix For: 0.10.0
>
>         Attachments: YETUS-679.00.patch
>
>
> Because dupname doesn't report in the case of success, the clock goes wonky in the report.  Another choice is to have some sort of catch-all that covers unreported tests.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)