Summary: | F1 build, W2 Test, java.io.Exception error. | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Konrad Kolosowski <konradk> | ||||||||
Component: | Update (deprecated - use Eclipse>Equinox>p2) | Assignee: | Dejan Glozic <dejan> | ||||||||
Status: | RESOLVED DUPLICATE | QA Contact: | |||||||||
Severity: | major | ||||||||||
Priority: | P3 | ||||||||||
Version: | 2.0 | ||||||||||
Target Milestone: | --- | ||||||||||
Hardware: | Power PC | ||||||||||
OS: | All | ||||||||||
Whiteboard: | |||||||||||
Attachments: |
|
Description
Konrad Kolosowski
2002-05-24 14:46:01 EDT
Created attachment 1044 [details]
metadata
O.K. It turned out that that I had not have enough space in the /tmp directory. I would never guess, and the error does not say this. Also you guys are deleting temporary files on exit, so checking disk space after exiting Eclipse reveals empty space. I will leave the bug open, so a better error message can be added. FeatureContentProvider#asLocalReference now catches any IOException during copying and transform them in CoreException("Unable to create file:"+file,e) Which will explain which file couldn't be created and hopefully tell the user where the space problem is. can you test it in next Integration build ? (not 20020528) in version v20020528H1015_17787 The error is still unclear in F2. I obtained the following error (see attachement) doing step C4 of the tests. Created attachment 1195 [details]
content of error dialog
I increased the space on /tmp, and after confirming the erorr dialog, I clicked finish (or install do not remember). The installation started and this time it showed me similar error dialog (attached) about jars being invalid, The error specified location of the jars in the /tmp directory. But the location that ran ouf of space should have been indicated in the previous dialog. Clicking finish should not allow installing features for which download failed, just to display another error. Created attachment 1199 [details]
second error dialog about invalid jars
|