cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johan Oskarsson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-164) Fix junit related build issues
Date Wed, 13 May 2009 09:16:46 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708841#action_12708841
] 

Johan Oskarsson commented on CASSANDRA-164:
-------------------------------------------

The problem is that then we won't get the junit xml files, which means hudson can't pick them
up and tell us what went wrong. I'll see if we can get both. 

As a side note I wish you wouldn't commit patches with additional, non reviewed changes. Personally
I think it's better to comment on the issue and let the developer make the changes or argue
a case against them.

> Fix junit related build issues
> ------------------------------
>
>                 Key: CASSANDRA-164
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-164
>             Project: Cassandra
>          Issue Type: Bug
>    Affects Versions: 0.3
>            Reporter: Johan Oskarsson
>            Assignee: Johan Oskarsson
>             Fix For: 0.3
>
>         Attachments: CASSANDRA-164.patch
>
>
> Since the junit switch no xml report files are generated and the build doesn't fail properly
if a test fails

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message