Community
Participate
Working Groups
I've solved the infrastructure problem so that the automated tests can run. The semantic resource tests will run with the next I build, but I've got a preview available now (in the URL field). There are 17 errors in the tests (no failures though). PW
Hi Paul, I have a question concerning the two first test errors that are about creation of files beneaths a folder retrived via System.getProperty("java.io.tmpdir"). Is it safe to use this location to create some files and does this system property end with a slash? Thanks and best regards, Ed
I haven't looked at the test code, but I had a chat with Ed about he issue. He seems to use the same code that we have in ResourceTest#getTempStore and FileSystemHelper#getTempDir, so this should work. May it be a problem with permissions for the test process?
My java.io.tmpdir == /tmp and I have write permissions there, as touch /tmp/tst.txt creates a valid file on the build machine (e4Build has valid permissions for both its build/test directories and tmp). It does not end with a slash. PW
Created attachment 159179 [details] Test error logs This is the .log file that was generated during the SfsTestSuite run. PW
Paul, I have checked in some fixes. Could you please try to rerun the tests. Thanks, Ed
I've tagged Resources and launched another test build. I'll update the URL field to point to where the tests will end up ... it should be up in about 1 hour. The map file has been updated for the following Bug changes: + Bug 302766. Test failures in org.eclipse.core.resources.semantic.test.suite (ASSIGNED) + Bug 303073. Refactoring of SFS Tests and Examples Plugins (ASSIGNED) + Bug 303079. Refresh Job for SemanticResourcesView should not be visible in Progress View (FIXED) + Bug 303081. SemanticFileStore returns invalid path after removal (FIXED) The following projects have changed: org.eclipse.core.resources.semantic org.eclipse.core.resources.semantic.examples org.eclipse.core.resources.semantic.test org.eclipse.ui.resources.semantic PW
Paul, I have just checked in a fix for the remaining test failure so that the tests should be green now. Ed
I checked and there's still a problem in today's build (I've updated the URL). With M5 this week maybe you need to release to the build? PW
(In reply to comment #8) > I checked and there's still a problem in today's build (I've updated the URL). > With M5 this week maybe you need to release to the build? > PW I will work on it today and have created a bug 308191 to track changes. Cheers, Ed
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. If you have further information on the current state of the bug, please add it. 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.
This is a mass change to close all e4 bugs marked with "stalebug" whiteboard. If this bug is still valid, please reopen and remove the "stalebug" keyword.
