Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 391014 - Consider removing "performance" target from CVS tests
Summary: Consider removing "performance" target from CVS tests
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 4.15 M3   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-03 09:31 EDT by David Williams CLA
Modified: 2020-01-23 11:07 EST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2012-10-03 09:31:18 EDT
As observed in bug 389857, the CVS performance tests take a long time (1.5 to 2 hours) and since this is not an "active" area of development, we should reconsider having a "performance target" for these tests. 

This is in the test.xml file, from 
eclipse.platform.team/tests/org.eclipse.team.tests.cvs.core
if I'm looking at it right. 

I'm opening this bug for discussion. That is, I do mean "consider" not necessarily "do". 

For the short term, (and maybe forever) we can control what tests we run from the releng side of things, but ... at some point ... if we really are not going to be running a performance test, seems like the target in the bundle should be removed (or, commented out? Or, maybe, another attribute used to indicated "long running" so we could compute different sorts of lists of tests to run depending on if we wanted to include long running ones or not?
Comment 1 Lars Vogel CLA 2019-11-27 07:41:41 EST
This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.
Comment 2 Paul Pazderski CLA 2020-01-11 11:52:39 EST
I was about to open a similar bug because those tests are currently failing with

> Could not connect to :pserver:${cvs_user}@${cvs_host}:${cvs_root}: Cannot locate host: ${cvs_host}

Looks like a misconfiguration but with changed infrastructure I would expect it will be rather hard to restore those tests. At the same time I have strong doubts anyone is still interested in those test results.
Comment 3 Eclipse Genie CLA 2020-01-11 11:53:50 EST
New Gerrit change created: https://git.eclipse.org/r/155645
Comment 4 Paul Pazderski CLA 2020-01-11 12:08:11 EST
Additional or alternative to my change I would expect that we need to remove "teamcsv" from the "testToRun" parameter in Jenkins job config for the performance tests.
Comment 6 Eclipse Genie CLA 2020-01-15 01:27:35 EST
New Gerrit change created: https://git.eclipse.org/r/155899
Comment 8 Eclipse Genie CLA 2020-01-17 01:37:11 EST
New Gerrit change created: https://git.eclipse.org/r/156044
Comment 10 Paul Pazderski CLA 2020-01-23 11:01:42 EST
Thanks for your help Alex. There is always an additional spot to miss for me.

Do you see something left? My goal to get those test from the performance test result page is reached.
Comment 11 Alexander Kurtakov CLA 2020-01-23 11:07:52 EST
We are done here.