Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 402751 - Infinite Loop? causing tests to time out and grow log too large to zip
Summary: Infinite Loop? causing tests to time out and grow log too large to zip
Status: RESOLVED DUPLICATE of bug 402779
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.2.1   Edit
Hardware: PC Linux
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-08 10:40 EST by David Williams CLA
Modified: 2013-03-08 18:58 EST (History)
0 users

See Also:

Attachments
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 David Williams CLA 2013-03-08 10:40:35 EST 
Not sure what the issue is yet, infrastructure?, specific test? but I think recent unit test runs have been hitting overall time limit (I think 9 or 12 hours?) and by then there are some test ran and producing output, but the log is too large for Hudson to "zip up" and make available to us, so we do not get a "summary view" of results. The log is filling up with "Null Pointer Exception" messages. 

Such as, see recent test on 

https://hudson.eclipse.org/hudson/view/Eclipse%20and%20Equinox/job/ep4-unit-lin64/ws/workarea/I20130307-2000/eclipse-testing/results/consolelogs/
Comment 1 David Williams CLA 2013-03-08 18:58:58 EST 
Not sure yet, but think this is more of a "hudson config" issue, than anything wrong with out tests. I've opened bug 402779 for that angle of it. And will attempt to work around that, by changing hudson settings.

*** This bug has been marked as a duplicate of bug 402779 ***