[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-dev] Found cause of junit failures...

While investigating the junit errors occuring on the build machine(linux), we discovered we were relying on the api:

IResource.getLocalTimestamp(), to help track for modifications....  

It turns out this is not a reliable method, because of timing differences of each OS - you can't rely on this to change as the file changes.
"getModificationStamp()" should always be used, once we switched to this api, all junits passed on linux.....
We will drop these changes to the build.

We also did a search to see other uses of this method, and turned up a couple in j2ee and server component areas...

We opened this defect:   https://bugs.eclipse.org/bugs/show_bug.cgi?id=160718

I recommend doing a quick search on your code prevent failures in the future.

Thanks - Chuck

Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle Park, NC
Email:  cbridgha@xxxxxxxxxx
Phone: 919-254-1848 (T/L: 444)