[
https://issues.apache.org/jira/browse/SQOOP-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234021#comment-14234021
]
Hudson commented on SQOOP-1833:
-------------------------------
UNSTABLE: Integrated in Sqoop2-hadoop200 #637 (See
[https://builds.apache.org/job/Sqoop2-hadoop200/637/])
SQOOP-1833: Sqoop2: Add elapsed time information to pre-commit hook (abraham:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=a4e0bfa51da951f7ae9f365368c55159e7abd699)
* dev-support/test-patch.py
> Sqoop2: Add elapsed time information to pre-commit hook
> -------------------------------------------------------
>
> Key: SQOOP-1833
> URL: https://issues.apache.org/jira/browse/SQOOP-1833
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.4
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Priority: Minor
> Fix For: 1.99.5
>
> Attachments: SQOOP-1833.patch, SQOOP-1833.patch
>
>
> As of SQOOP-1777 we're running integration tests as part of the pre-commit
> hook and as we will add more and more tests, I think that it would be useful
> to also have an idea how long the pre-commit hook needs to execute.
> Whereas this information is available on Jenkins, I'm assuming that people
> won't be checking it there at all and hence I would like to build in such
> capability directly into the hook and simply print out in each Sqoop QA bot
> comment how long it took to test given patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
