Comments you submit will be routed for moderation. If you have an account, please log in first.
Modify

Ticket #3800 (closed defect: invalid)

Opened 5 years ago

Last modified 5 years ago

Hudson test script problem - copying old results

Reported by: wehart Owned by: jdsiiro
Priority: major Milestone: FAST 2.1
Component: FAST Version:
Keywords: Cc:

Description

The recent FAST builds expose a problem with our current testing scripts:

FAST_trunk_python2.4 (#9)
FAST_trunk_python2.5 (#10)

Both of these have a similar console output, in which FAST fails to import correctly. HOWEVER, the 2.5 test generates results!

I think that the test results in 2.5 are being copied over into the build directory. So, it looks like the 2.5 build is generating data when it is not!

I'm not sure how to recommend a fix for this. We could recursively delete TEST*xml, but that only applies to that type of test artifact (which, admittedly, is the most important one.

Attachments

Change History

comment:1 Changed 5 years ago by jdsiiro

I really don't see how "test results are being copied over"... The build script blows away the entire build directory each time, and copies over a clean starting point from the checkout directory (which should never be touched, except by svn checkout / update).

The 2.5 build you reference *is* different from the 2.4 build: it actually appears to run tests and generate code coverage, whereas the 2.4 build looks to out-and-out fail to run.

The real problem here is that it appears that we cannot rely on the exit code of the test script to determine failure (it appears to return non-zero when any of the tests fail -- even when the script ran successfully). Really, we want the test script to only return non-zero when the script itself failed -- that way, we can pass that failure out to Hudson as a "build failure", and not just that there were fewer tests to run this time around.

comment:2 Changed 5 years ago by wehart

  • Status changed from new to closed
  • Resolution set to invalid

This ticket is invalid. The virtual python environment was not being setup correctly, except for in Python 2.5. Go figure...

I added a fix to the script that sets up the virtual python environment, which seems to do the trick!

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.