[
https://issues.apache.org/jira/browse/DERBY-4157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12723651#action_12723651
]
Rick Hillegas commented on DERBY-4157:
--------------------------------------
I have changed my mind about how many seconds make up an hour. Previously I
estimated that it would take 19 days to test all of the upgrade trajectories.
That was based on a belief that there were 360 seconds in an hour. I now think
that on our planet, 3600 is a better figure. Given an hour that lasts 3600
seconds, it should only take around 2 days to test all of the trajectories. If
you are interested in double-checking my arithmetic and beliefs, here's the
formula I'm using:
Result = ( ( Trajectories * SecondsPerTrajectory ) / SecondsInHour ) /
HoursInDay
Trajectories = ((2**14) - 14) - 1 = 16369
SecondsPerTrajectory = 10
SecondsInHour = 3600
HoursInDay = 24
Result = 1.9 days
> Create a test to verify that virgin metadata is identical to hard-upgraded
> metadata
> -----------------------------------------------------------------------------------
>
> Key: DERBY-4157
> URL: https://issues.apache.org/jira/browse/DERBY-4157
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.6.0.0
> Reporter: Rick Hillegas
> Assignee: Rick Hillegas
> Attachments: derby-4157-01-aa-refactor.diff,
> derby-4157-02-aa-newtest.diff, derby-4157-02-ab-newtest.diff
>
>
> We should write a test to verify that the metadata is correct for each
> release for all hard-upgrade trajectories which terminate in that release.
> The test should examine all system tables. Note that if there are N releases,
> then there will (2<sup>N</sup> - N) - 1 trajectories to examine.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
