Community
Participate
Working Groups
We have run org.ecliipse.jdt.core.tests.model in HP_UX several times before and it has always passed 100%. But today we ran it against Eclipse 3.0.1RC2 and it has passed 97.11% (120 Errors & 1 Failure) All the errors seems to have the same problem as attached. When we gave 777 permission to eclipse-testing folder, then only 4 tests have failed. Can somebody help us to correct this behaviour.
Created attachment 14487 [details] test results
It looks like IFile.setReadOnly(false) failed on your system. This can either be a VM bug, or a bug with your OS. Do you know any latency the OS could have when setting the readonly flag ?
but how did it work for even 3.0.1RC1. In 3.0.1RC1, all the test cases passed (100%). Is this is a new change between 3.0.1RC1 & 3.0.1RC2?
There were no change at the JDT Core level in this area. DJ any change around the readonly flag in Platform Resources ?
No, that's strange. I just checked and our HP-UX library hasn't changed since June and the only thing that we changed in Core-Resources between those builds were removing unused import statements. I presume that the tests were run several times and the same results happened each time?
Yes , we have run these tests atleast for 3 times today. We have encountered the same results. But when we gave 777 permission to eclipse-testing folder , we got only 4 errors while running these tests. Does this give any clue ?
No idea. You should post the results from the 4-errors run as well so we can see if there are real problems there too. Thanks.
Created attachment 14490 [details] Test results with only 4 errors
So only the conditions you run the tests can have changed (since there was no code change at the Eclipse level). 1. Are you using the same VM to run the tests in RC1 and RC2 ? 2. Are you using the same OS version to run the tests in RC1 and RC2 ? 3. Are you using the same machine to run the tests in RC1 and Rc2 ?
'Yes' to all. -Ragav.
To summarize there are no change on the Eclipse side, there is no change on your side. Since I don't have access to HP-UX, I can only help you debug it. To debug it, you need to check out org.eclipse.jdt.core.tests.compiler and org.eclipse.jdt.core.tests.model from dev.eclipse.org (take the v_452_R30x version). Add a breakpoint in the test that is failing. Run AllJavaModelTests in debug mode.
We ran org.ecliipse.jdt.core.tests.model test suite today with the build "200409151412". It has passed successfully (100%). We have not made any change in the code and neither there is any change in the system set up. Can you tell us if this gives you some clue ? Thanks for your time
Sorry but JDT Core didn't change anything in this area in 200409151412 (we didn't even change a single line of code between 3.0.1 and M200409151412)
Looks like we get this error in the alternate builds. We got the same errors again in Eclipse 3.0.1. We are sure that there is no change in the system environment. I know the response is misleading but this is what we are getting.
This problem cannot be reproduced. Nothing JDT Core can do. Closing as third party problem.
