Bugzilla – Full Text Bug Listing
| Summary: | [model] [test] testMissingClasspath fails on test machine | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Satyam Kandula <satyam.kandula> |
| Component: | Core | Assignee: | Jay Arthanareeswaran <jarthana> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | amj87.iitr, david_williams, jarthana, manoj.palat, markus.kell.r, shankhba, srikanth_sankaran, stephan.herrmann |
| Version: | 3.8 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | stalebug | ||
|
Description
Satyam Kandula
This runs fine on my workspace.. (In reply to comment #1) > This runs fine on my workspace.. Passes for me too. Perhaps a red herring. (In reply to comment #2) > (In reply to comment #1) > > This runs fine on my workspace.. > > Passes for me too. Perhaps a red herring. Fine in my workspace, consistently broken also in Object Teams build. If a herring then it is pink at best :) (In reply to comment #3) > Fine in my workspace, consistently broken also in Object Teams build. If a > herring then it is pink at best :) Where does the Object Teams tests run? Do you have an idea from when this could have started failing? (In reply to comment #4) > Where does the Object Teams tests run? build.eclipse.org > Do you have an idea from when this could have started failing? Sorry, no, I forgot to record this, but most likely at the time when I adopted JDT/Core's changes from M6 to M7. If you have an idea what information should be logged during tests I can happily try to pull out more info from the Object Teams build. I noticed a similar thing happen with the latest win-32 build (4.2). Steps to reproduce: 1. Create a java project 2. Close the project 3. Go to windows explorer and delete the .classpath from the project 4. Go back to Eclipse and open the project (with build automatically enabled) There should be an error about the missing classpath but there isn't. I am suspicious about the code inside JavaProject#readFileEntriesWithException(). First the condition rscFile.exists() returns "true" but later the check file.exists() returns false. Investigating further. (In reply to comment #6) > There should be an error about the missing classpath but there isn't. I am > suspicious about the code inside JavaProject#readFileEntriesWithException(). > First the condition rscFile.exists() returns "true" but later the check > file.exists() returns false. Investigating further. Sorry, that's not what I really wanted to say. What I really meant to say was that we return an empty classpath when the classpath file doesn't exist. This results in an 'OK' status being sent to ClasspathValidation.validate(). The test failure is still not reproducible locally and fails only in win-32 set-up during build. This doesn't appear to be affecting the build (despite my observations in comment #6, since I see that behavior with IDE even with older builds) While I am investigating further, I have disabled the tests temporarily. (In reply to comment #8) > The test failure is still not reproducible locally and fails only in win-32 > set-up during build. I also see it during build&test on Linux. (In reply to comment #9) > I also see it during build&test on Linux. Stephan, are you seeing the failures on your machine or the build environment? (In reply to comment #10) > (In reply to comment #9) > > I also see it during build&test on Linux. > > Stephan, are you seeing the failures on your machine or the build environment? build environment, headless build on build.eclipse.org, to be specific. Build ID: N20140626-2000 Platform: Linux Test Location: http://download.eclipse.org/eclipse/downloads/drops4/N20140626-2000/testresults/html/org.eclipse.jdt.core.tests.model_linux.gtk.x86_64_8.0.html Failed again. Thanks Location: http://download.eclipse.org/eclipse/downloads/drops4/N20140627-2000/testresults/html/org.eclipse.jdt.core.tests.model_linux.gtk.x86_64_8.0.html Build ID: N20140627-2000 Platform: Linux Failed again. http://download.eclipse.org/eclipse/downloads/drops4/N20140628-1500/testresults/html/org.eclipse.jdt.core.tests.model_linux.gtk.x86_64_8.0.html Build ID: N20140628-1500 Platform: Linux Failed again. Was the test just newly re-enabled? Seems for fail consistently each N-build, on all platforms ... ever sense we restarted builds after Luna release. *** Bug 438507 has been marked as a duplicate of this bug. *** (From bug 438507 comment #5) > The test is a regression test for bug 39877, and the implementation looks > valid to me. It would be good to know why the test fails. It is green > locally, even when I add an explicit > preferences.setAutoBuilding(...); > with false or true. The test has been disabled with bug 438507 comment 4 (on 2014-06-30). This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |