stdcxx-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Sebor (JIRA)" <j...@apache.org>
Subject [jira] Updated: (STDCXX-734) enhacements for the results/builds page
Date Tue, 20 May 2008 22:02:55 GMT

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

Martin Sebor updated STDCXX-734:
--------------------------------

    Affects Version/s: 4.2.0
                       4.2.1
        Fix Version/s: 4.2.2
             Assignee: Martin Sebor

The pages have moved to http://stdcxx.apache.org/builds/.

Assigned to self and scheduled for 4.2.2.

> enhacements for the results/builds page
> ---------------------------------------
>
>                 Key: STDCXX-734
>                 URL: https://issues.apache.org/jira/browse/STDCXX-734
>             Project: C++ Standard Library
>          Issue Type: Improvement
>          Components: Test Harness
>    Affects Versions: 4.2.0, 4.2.1
>            Reporter: Martin Sebor
>            Assignee: Martin Sebor
>            Priority: Critical
>             Fix For: 4.2.2
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> The [Available Multi-platform Build Result Views|http://people.apache.org/~sebor/stdcxx/results/builds]
page generated by the {{[xgenviews|http://svn.apache.org/repos/asf/stdcxx/trunk/bin/genxviews]}}
script needs to be enhanced in a number of ways in order to be more useful. Some the important
enhancements include:
> * The age of the oldest and youngest builds for each platform/row. This is important
in order to quickly discover platforms that aren't churning out builds
> * The status of the worst (and perhaps also the best) builds for each platform/row. This
is important so that we can see, at a glance, which platforms have the most serious problems
and thus might need immediate attention.
> * The presence of regressions in any of the builds for each platform/row. This one would
be +extremely+ useful in helping us find breakage introduced during development.

-- 
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