| Summary: | Errors loading existing .eclipseextension install folder w/ p2 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Nick Boldt <nboldt> | ||||
| Component: | p2 | Assignee: | Simon Kaegi <simon_kaegi> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | dj.houghton, pascal, simon_kaegi, susan | ||||
| Version: | 3.4 | ||||||
| Target Milestone: | 3.4 M7 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 229641 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Nick Boldt
Thanks for the detailed logs. I'm removing the blocking bug because I don't think the patched jar has anything to do with it. I think it's a coincidence and the real problem may involve cleaning and retrying the scenario each time. Either something got destroyed during the cleaning, or something bad happened in p2 as a result of that seemingly successful install. It appears that a core cache is missing (not sure if it's the bundle pool itself or a repo cache.) In c:\temp\eclipse_I2008032401300.install.mylyn.from.eclipseextension.folder.patched.txt, the problem is here: !ENTRY org.eclipse.equinox.p2.ui 4 0 2008-03-25 19:09:18.981 !MESSAGE Unable to load the repository file:/x/home/nickb/eclipse/34clean/eclipse/p2/org.eclipse.equinox.p2.core/cache/ !STACK 1 org.eclipse.equinox.internal.provisional.p2.core.ProvisionException: No repository found at file:/x/home/nickb/eclipse/34clean/eclipse/p2/org.eclipse.equinox.p2.core/cache/ Pascal/Simon - is this the bundle pool or some other cache? Something important is gone. In c:\temp\eclipse_I2008032401300.install.mylyn.from.eclipseextension.folder.patched.bad.txt, it looks like an asynch refresh of the available features view occurred during restart. Something must have finished installing, and the platform tried to restart, and during this time, a viewer that was either partially created or had been destroyed during the restart was trying to refresh. This is the kind of thing the UI should code around with disposed and null checks. I annotated bug #bug 224004 with this info. I verified that this works correctly now. It requires the fix in bug 229641. I'm going to mark this as a "Depends on" but then come back and close this after we're done with that bug. Marking Fixed along with 229641. |