[
https://issues.apache.org/jira/browse/HIVE-14572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15431412#comment-15431412
]
Zoltan Haindrich commented on HIVE-14572:
-----------------------------------------
[~sseth] i've found a possibly related jenkins/junit plugin ticket
(https://issues.jenkins-ci.org/browse/JENKINS-36819
)...and by using junit plugin 1.10 the anomaly is gone...but it doesn't account
for before/after timings anymore ; so all 2.16 and 2.19.1 timings are 1.2sec-s
- but at least it is consistent.
what do you think - a plugin downgrade would be acceptable?
I've seen a few time aggregation related tickets filed against this plugin
lately...so someone might be possibly working on it... i will peek into the
plugin code - maybe I will be able to give them at least a unit test for the
problem...
> Investigate jenkins test report timings
> ---------------------------------------
>
> Key: HIVE-14572
> URL: https://issues.apache.org/jira/browse/HIVE-14572
> Project: Hive
> Issue Type: Sub-task
> Components: Tests
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
>
> [~sseth] have noticed some odd timings in the jenkins reports
> I've created a sample project, to emulate a clidriver run during qtest:
> the testclass:
> * 1 sec beforeclass
> * 3x 0.2s test
> created using junit4 parameterized.
> Double checkout; second project runs different tests...or at least they have
> different name.
> here are my preliminary findings:
> || thing || expected || 2.16 || 2.19.1
> | total time | ~3.4s | 1.2s | 3.4s
> | package time | ~3.4s | 0.61s | 1.7s
> | class time | ~3.4s | 0.61s | 1.7s
> | testcase times | ~.2s | ~.2s | ~.2s
> notes:
> * using 2.16 beforeclass timngs are totally hidden or lost
> * 2.19.1 does account for beforeclass but still fails to correctly aggregate
> the two runs of the similary named testclasses
> it might worth a try to look at the bleeding edge of this jenkins plugin...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
