db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3045) Write a tool to do a binary search of past trunk builds to find the source of regressions
Date Tue, 04 Sep 2007 16:20:51 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524777
] 

Daniel John Debrunner commented on DERBY-3045:
----------------------------------------------

What's a "trunk jar from a previous release"? Releases are off branches, not the trunk?

Also why keep any jars around, the jars can be re-built from a codeline at the correct revision?
In some cases the regression might have been caused by one of three changes included in a
set of built jars, so the built jars may not always lead to the specific change.



> Write a tool to do a binary search of past trunk builds to find the source of regressions

> ------------------------------------------------------------------------------------------
>
>                 Key: DERBY-3045
>                 URL: https://issues.apache.org/jira/browse/DERBY-3045
>             Project: Derby
>          Issue Type: Task
>          Components: Build tools
>    Affects Versions: 10.4.0.0
>            Reporter: Kathey Marsden
>
> Often we have to backtrack to find the source of a regression.   It would be useful to
have a tool which would run a java program against archived builds and do a binary search
for the build that caused the failure.  Trunk builds for the current release are stored at
http://dbtg.thresher.com/derby/bits/trunk/ but in order for the tool to be most useful we
would need to start keeping the trunk jars from previous releases.

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