Bugzilla – Full Text Bug Listing
| Summary: | [releng] build failed with director error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] e4 | Reporter: | Paul Webster <pwebster> | ||||
| Component: | UI | Assignee: | Project Inbox <e4.ui-inbox> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | aniefer, remy.suen | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Marking as duplicate of 342957, still don't know the cause here. This log has a few [p2.director] String index out of range: 39905 entries. The stack trace seen in the log was handled and logged by p2, so it wasn't the actual "stopper". In particular, the NPE is caused by a null bundle context object, indicating the Director app bundle had actually been stopped by osgi. (or had never been started? don't think this could happen). Because we are doing director calls in parallel, I think it is possible that some other thread caused a problem, causing the framework to shutdown, and this thread wasn't done yet. For lack of anything better to do, I increased the amount of memory used for the build and decreased the number of parallel calls from 4 to 3 to reduce memory use. The build was restarted at 10:40 and appears to be proceeding without problem. *** This bug has been marked as a duplicate of bug 342957 *** |
Created attachment 195200 [details] Log with director errors It's not clear what's going on, but the build failed with some director grumpiness. I've cut the log off and attached. PW