Community
Participate
Working Groups
See, for example, https://hudson.eclipse.org/perftests/job/ep46I-perf-lin64-baseline/ws/workarea/I20151103-0800/eclipse-testing/results/linux.gtk.x86_64_8.0/org.eclipse.team.tests.ccvs.ui.benchmark.SyncTests.txt While I think these could be made to run, if we installed a "local cvs system", on the performance machine itself, that seems like a lot of overhead, at the moment. (It not a simple "one-time thing" since we want the performance tests to run on several machines ... in addition to "local builds"). Plus, in the big scheme of things, I wonder how important they are? Guess that depends on how "CVS specific" they are. So, I suggest for now we disable the CVS tests for performance tests and open an enhancement to re-enable them. (As part of that re-enablement, BTW, I do not know why the CVS unit tests can not "create their own CVS installation" if one found not to exist. Obviously, would depend on 'cvs' being installed on the system, and, I know there would be issues with userid and password, but ... suspect there are adequate solutions to those, rather depending on "pre-creation". If does depend on "pre-creation, perhaps a "protected script" could be provided to automate it? By that, I mean "protected" in that it would not expose a password, but that be the one thing needed to be "filled in" when ran?)
CCing Dani, to see if he agrees, or if I am "off-base".
A related test, I see now, is https://hudson.eclipse.org/perftests/job/ep46I-perf-lin64-baseline/ws/workarea/I20151103-0800/eclipse-testing/results/linux.gtk.x86_64_8.0/org.eclipse.team.tests.ccvs.ui.benchmark.WorkflowTests.txt I propose it be disabled too, for performance tests.
BTW, this is a little off-topic of this bug, but I have noticed in "Automated tests set up instructions" (somewhere?) it mentions setting up the CVS repo, and how to, and then says "... and, should be clean up occasionally since over time it can get large ...". Well, I have never "cleaned up", in the past several years, so if that is still required, can you explain that more, or provide script? Or, perhaps even add to the CVS Unit tests? [I can open a new bug, depending on your response and preference.]
CVS performance tests haven't been run for long time.
