Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345259 - [releng] build failed with director error
Summary: [releng] build failed with director error
Status: CLOSED DUPLICATE of bug 342957
Alias: None
Product: e4
Classification: Eclipse Project
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-10 08:19 EDT by Paul Webster CLA
Modified: 2011-05-10 11:40 EDT (History)
2 users (show)

See Also:

Attachments
Log with director errors (289.21 KB, text/plain)
2011-05-10 08:19 EDT, Paul Webster CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Webster CLA 2011-05-10 08:19:52 EDT 
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
Comment 1 Andrew Niefer CLA 2011-05-10 11:40:33 EDT 
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 ***