[
https://issues.apache.org/jira/browse/ANY23-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16437497#comment-16437497
]
ASF GitHub Bot commented on ANY23-337:
--------------------------------------
GitHub user HansBrende opened a pull request:
https://github.com/apache/any23/pull/78
ANY23-337 fixed: BenchmarkTripleHandler reported inaccurate runtimes
mvn clean test -> all tests pass
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/HansBrende/any23 ANY23-337
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/any23/pull/78.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #78
----
commit c0db95e7c370eac13bbfcb9018eb960295a12faa
Author: Hans <firedrake93@...>
Date: 2018-04-13T16:07:03Z
ANY23-337 fixed: BenchmarkTripleHandler reported inaccurate runtimes
----
> BenchmarkTripleHandler does not report accurate extraction interval times
> -------------------------------------------------------------------------
>
> Key: ANY23-337
> URL: https://issues.apache.org/jira/browse/ANY23-337
> Project: Apache Any23
> Issue Type: Bug
> Components: core, extractors
> Affects Versions: 2.2
> Reporter: Hans Brende
> Priority: Major
> Fix For: 2.3
>
>
> The begin and end-time statistics of the BenchmarkTripleHandler are recorded
> in TripleHandler.openContext(), and TripleHandler.closeContext(),
> respectively. However, neither of these methods are called until *after the
> extraction has already completed*, resulting in extraction times that
> approach zero!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
