[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-releng-dev] Performance re-testing on releases and 3.1 milestones
|
Mike,
tests often use internal code and hence they get broken even if the API is
kept stable.
Dani
Mike Wilson
<Mike_Wilson@ca.i
bm.com> To
Sent by: "Eclipse platform release
platform-releng-d engineering list."
ev-bounces@eclips <platform-releng-dev@xxxxxxxxxxx>
e.org cc
Subject
13.04.2005 14:54 Re: [platform-releng-dev]
Performance re-testing on releases
and 3.1 milestones
Please respond to
"Eclipse platform
release
engineering
list."
<platform-releng-
dev@xxxxxxxxxxx>
What you are saying is that, at 3.1 M5 you were not compatible with 3.0. I
would expect this to be the uncommon case. In any case, your tests will
just fail then. It's up to you to decide if you want to re-write them in a
way that works around your incompatibility.
McQ.
Wassim Melhem/Toronto/IBM@IBMCA
Sent by: platform-releng-dev-bounces@xxxxxxxxxxx
04/13/05 02:17
Please respond to
"Eclipse platform release engineering list."
To
"Eclipse platform release engineering list."
<platform-releng-dev@xxxxxxxxxxx>
cc
Subject
Re: [platform-releng-dev] Performance re-testing on releases and 3.1
milestones
Here is the problem:
Internal code has changed significantly throughout the 3.1 cycle.
You can't expect performance test cases that are written against 3.0.x
code
(i.e. the perf_30 branch) to just compile and run against 3.1M1-M5.
We need to "like" have a branch for every milestone, or we could just skip
the 3.1 milestones altogether and just use the latest 3.1 from HEAD.
Wassim.
Sonia
Dimitrov/Ottawa/I
BM@IBMCA To
Sent by: platform-releng-dev@xxxxxxxxxxx
platform-releng-d cc
ev-bounces@eclips
e.org Subject
[platform-releng-dev] Performance
re-testing on releases and 3.1
04/12/2005 05:17 milestones
PM
Please respond to
"Eclipse platform
release
engineering
list."
Starting this Friday, we would like to run performance tests on previous
releases (starting at 2.1.3) and 3.1 milestones to generate a new history
of performance measurements on four newly configured performance test
machines. These will consist of two identical "slower" machines (Intel P4
2 GHz, 512 MB RAM) and two identical "fast" machines (Intel P4 3 GHz, 2
gig
RAM) which will run Windows XP (SP1) and Red Hat Enterprise Linux WS 3.
This task will require approximately 80 hours to complete and if all goes
smoothly, we expect to have all the re-testing done by Wednesday April 20.
Please see
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-releng-home/performance_test_plan.htm
for further details and background.
In order for us to proceed, we ask ALL teams using CPU Time in assertions
and summaries (ie. fingerprints) to switch to using Elapsed Process in
HEAD
and perf_* streams of your tests where needed by 11pm (Ottawa time)
Thursday, April 14.
Please respond to this list with questions or comments.
Sonia _______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
_______________________________________________
platform-releng-dev mailing list
platform-releng-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-releng-dev
