Builder integration-explicitAnalysis Build #271

Results:

Warnings

SourceStamp:

BuildSlave:

Reason:

scheduler

Steps and Logfiles:

1. svn update ( 20 secs )
   1. stdio
2. Local mods Ran ( 0 secs )
   1. stdio
3. shell 'ant' ( 14 secs )
   1. stdio
4. shell_1 benchmark.py ( 22 mins, 48 secs )
   1. stdio
5. setproperty 5 properties set ( 0 secs )
   1. stdio
   2. property changes
6. shell_2 Cleanup results ( 0 secs )
   1. stdio
7. shell_3 regression.py ( 0 secs )
   1. stdio
8. shell_4 table_generator.py ( 0 secs )
   1. stdio
9. MasterShellCommand Ran ( 22 secs )
   1. stdio
10. shell_5 Prepare results 2 ( 0 secs )
    1. stdio
11. Transfer results uploading results ( 1 secs )
    1. - no logs -
12. Final result Final result ( 0 secs )
    1. - no logs -
    2. TABLE

Build Properties:

Blamelist:

1. pwendler

Timing:

Resubmit Build:

All Changes:

1. Change #360

   Changed by	pwendler
   Changed at	Mon 20 Feb 2012 14:21:31
   Repository	https://svn.sosy-lab.org/software/cpachecker/trunk
   Revision	5669

   Comments

   Catch OutOfMemoryErrors during loop detection.
   
   Usually one should not catch Errors, but this is a special case.
   The operation here is optional, and the analysis might well have the chance
   to continue without it.
   Furthermore, aborting the loop detection will usually free some amount
   of memory immediately because a lot of objects fall out of scope,
   so we probably don't hit the memory limit immediately again.
   
   See #70 for a file which triggers an OOM during loop detection with
   default heap size.

   Changed files

   • src/org/sosy_lab/cpachecker/cfa/CFACreator.java