continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SebbASF (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (CONTINUUM-2428) Failed Build results do not always agree with e-mail
Date Sun, 10 Jan 2010 11:43:55 GMT

    [ http://jira.codehaus.org/browse/CONTINUUM-2428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=206070#action_206070
] 

SebbASF commented on CONTINUUM-2428:
------------------------------------

Should have clarified - only for BuildId 267099 do the e-mail and online report agree.
The link to the Surefire report is also OK.

For the other e-mails, it looks like the Test Summary and Test Failures are taken from the
previous failure.

Furthermore, the SureFire reports, for example:

http://vmbuild.apache.org/continuum/surefireReport.action?buildId=267134&projectId=22
linked from on the page
http://vmbuild.apache.org/continuum/buildResult.action?buildId=267134&projectId=22

are in fact the output from the last failed run.

This is possibly related to the fact that BuildIds 267134 and 267250 were flagged as Failed
rather than Error.


> Failed Build results do not always agree with e-mail
> ----------------------------------------------------
>
>                 Key: CONTINUUM-2428
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2428
>             Project: Continuum
>          Issue Type: Bug
>         Environment: Version:         1.3.4-SNAPSHOT
> Build Number:   790494
>            Reporter: SebbASF
>            Priority: Critical
>         Attachments: ContinuumBugs.zip
>
>
> The e-mail sent for a failed build has a link to the build results.
> One would expect the build outputs to agree with each other, but that is not always the
case.
> See the attached examples. Here is the build result summary covering the runs.
> Corresponding buildId in () at the end
> {code}
>     Jan 08, 2010 06:29:25 AM PST Jan 08, 2010 06:29:34 AM PST Duration : 9 sec      
 Failed (267250)
>     Jan 08, 2010 06:29:19 AM PST Jan 08, 2010 06:29:25 AM PST Duration : 5 sec 	    
 Error  
>     Jan 08, 2010 03:45:43 AM PST Jan 08, 2010 03:45:46 AM PST Duration : 3 sec 	    
 Error
>     Jan 08, 2010 01:49:48 AM PST Jan 08, 2010 01:49:57 AM PST Duration : 8 sec 	    
 Failed (267134)
>     Jan 08, 2010 01:49:31 AM PST Jan 08, 2010 01:49:39 AM PST Duration : 7 sec      
 Error
>     Jan 08, 2010 12:33:12 AM PST Jan 08, 2010 12:35:04 AM PST Duration : 1 min 51 sec
Failed (267099)
> 133 Jan 07, 2010 03:29:05 PM PST Jan 07, 2010 03:30:27 PM PST Duration : 1 min 21 sec
Success
> {code}
> It looks like the reporting of failed runs is badly broken.
> Two of the runs marked as Failed must actually have been Error, because the run-time
is too short.
> No mails appear to have been sent for the runs marked as Error.
> Furthermore, the Failed e-mails contain a "Build Number" that is irrelevant.
> Another (minor) issue is that the times are reported in different formats: sometimes
PST, sometimes -0800.
> It would be best if the -0800 was always used.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message