Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-releng] Smoke Test Request for WTP 3.2.0 I-build

The jpt utility failures are all infrastructure (and our test code) related and do not affect the fitness of the build.  As we increase the timeout values of the test runs, we also need to increase timing ranges in our utility tests.  We'll adjust these ranges for next week's I-Build.


David M Williams wrote:

Here's the URL of the finished build, at the 'committers' area  ...

... the tests did complete ... sort of.

I actually kill the jsf.designtime tests after they had ran over an hour ... trying to keep within the 5 hour overall limit.

There were also 5 failures in jpt utility tests that should be investigated, to see if we need a re-build, or if just test/infrastructure issues.

I'll increase the overall limit to 6 hours. If we time out then, I think we'll need other options.

From: David M Williams/Raleigh/IBM@IBMUS
To: wtp-releng@xxxxxxxxxxx
Date: 02/18/2010 12:20 PM
Subject: [wtp-releng] Smoke Test Request for WTP 3.2.0 I-build
Sent by: wtp-releng-bounces@xxxxxxxxxxx

Smoke Test Request for WTP 3.2.0 I-build

Please document your Project's testing and approval of build, by Thursday,
5 PM (Eastern Time), or let us know if that's not possible.

Notice this build URL points to the "active" build ... the unit tests have
not yet completed. But, I think it might be worth smoke testing, if teams
do not mind the (slight) risk of having to re-test, if large issues found.

The tests seem to be progressing normally, but slowly, due to busy server.
My fear is these tests (and maybe previous build) hit the overall 5 hour time

limit we have set for the test runs. I increased the individual time limit

to 1.5 hours (up from 1 hour) as discussed at last status meeting (and,
sure enough, jpt.core.tests took slightly over one hour today, instead of
the usual 45 minutes). But ... if many tests take "more than an hour",
then we are more likely to hit the overall time limit ... instead of
individual tests Not Finishing. (In other words, even this build may hit

5 hour time limit, and then I'd begin to wonder if we should 'declare
with caution' rather than wait overnight for new test run?

Current Build

Smoketest Results
wtp-releng mailing list

_______________________________________________ wtp-releng mailing list wtp-releng@xxxxxxxxxxx

Back to the top