You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Sqoop QA bot (JIRA)" <ji...@apache.org> on 2014/11/23 03:31:12 UTC

[jira] [Commented] (SQOOP-1783) Sqoop2: Create derby integration upgrade tests

    [ https://issues.apache.org/jira/browse/SQOOP-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222288#comment-14222288 ] 

Sqoop QA bot commented on SQOOP-1783:
-------------------------------------

Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12683199/SQOOP-1783.patch against branch sqoop2.

{color:red}Overall:{color} -1 due to an error

{color:red}ERROR:{color} failed to apply patch (exit code 1):
{code}error: cannot apply binary patch to 'test/src/test/resources/repository/derby/derby-repository-1.99.4.tar.gz' without full index line
error: test/src/test/resources/repository/derby/derby-repository-1.99.4.tar.gz: patch does not apply
{code}

{color:green}SUCCESS:{color} Clean was successful

Console output: https://builds.apache.org/job/PreCommit-SQOOP-Build/653/console

This message is automatically generated.

> Sqoop2: Create derby integration upgrade tests
> ----------------------------------------------
>
>                 Key: SQOOP-1783
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1783
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.4
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>             Fix For: 1.99.5
>
>         Attachments: SQOOP-1783.patch, derby-repository-1.99.4.tar.gz
>
>
> During my validation of 1.99.4 release, I've several times run upgrade scenario when I took repository generated by previous release and let the new release upgrade the structures. We've found several bugs during this manual exercise as we did several changes and we don't have any test coverage in this area. Hence for future releases I would like to introduce automatic upgrade tests that would run as a part of our integration test suite.
> I'm currently thinking of doing exactly what I've done in my manual exercise. We can create example derby repository that is exercising various different values for (all) previous releases and store that an archive with the code. The integration tests will then untar the stored archive and simply run the upgrade procedure This approach won't guarantee that we will catch all upgrade bugs, but will provide reasonable confidence that we can release the new bits without additional manual testing.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)