How to stop build analysis?

[Andrew Prentice]

Several builds of a single project (Project A) triggered by one of our
CI servers have failed (due to java.lang.OutOfMemoryError: Java heap space)

The Sonar project/list dashboard states
"Currently analysing *Project A* (for about 19 hours), *Project A* (for
about 3 hours), *Project A* (for about 2 hours), *Project A* (for 36
minutes), and *Project B* (for 18 minutes)"

The Project B build did not fail but it appears its analysis is being
prevented by the previous Project A builds.  Is there a recommended way
for stopping the analysis of failed builds as restarting the server does
not do this?

I'm running Sonar 1.1 with MySQL 5.0.51a on OSX 10.5.1

FYI - snapshot_id for builds listed above are 71-75
mysql> select * from snapshots
    -> where id >='70';
+----+---------------------+---------------+------------+--------------------+--------+--------+--------+
| id | created_at          | version       | project_id |
parent_snapshot_id | status | purged | islast |
+----+---------------------+---------------+------------+--------------------+--------+--------+--------+
| 70 | 2008-03-03 14:44:33 | 4.0-SNAPSHOT  |         70 |              
NULL | P      |      0 |      1 |
| 71 | 2008-03-03 17:10:45 | 4.0-SNAPSHOT  |         70 |              
NULL | C      |      0 |      0 |
| 72 | 2008-03-04 09:25:09 | 4.0-SNAPSHOT  |         70 |              
NULL | T      |      0 |      0 |
| 73 | 2008-03-04 10:04:43 | 4.0-SNAPSHOT  |         70 |              
NULL | T      |      0 |      0 |
| 74 | 2008-03-04 11:44:48 | 4.0-SNAPSHOT  |         70 |              
NULL | T      |      0 |      0 |
| 75 | 2008-03-04 12:02:52 | 3.11-SNAPSHOT |          1 |              
NULL | T      |      0 |      0 |
+----+---------------------+---------------+------------+--------------------+--------+--------+--------+

Regards,
Andrew

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Simon Brandhof-3]

Hi Andrew,

Could you please attach the server logs ?

- stop the server
- delete the files logs/*
- edit conf/logback.xml and set the INFO level :
  <root>
    <level value="INFO"/>
    <appender-ref ref="SONAR_FILE"/>
  </root>
- restart the server
- wait a few minutes and logs are ready !

Thank you
Simon

On Tue, Mar 4, 2008 at 3:15 AM, Andrew Prentice <[hidden email]> wrote:

> Several builds of a single project (Project A) triggered by one of our
> CI servers have failed (due to java.lang.OutOfMemoryError: Java heap space)
>
> The Sonar project/list dashboard states
> "Currently analysing *Project A* (for about 19 hours), *Project A* (for
> about 3 hours), *Project A* (for about 2 hours), *Project A* (for 36
> minutes), and *Project B* (for 18 minutes)"
>
> The Project B build did not fail but it appears its analysis is being
> prevented by the previous Project A builds.  Is there a recommended way
> for stopping the analysis of failed builds as restarting the server does
> not do this?
>
> I'm running Sonar 1.1 with MySQL 5.0.51a on OSX 10.5.1
>
> FYI - snapshot_id for builds listed above are 71-75
> mysql> select * from snapshots
>    -> where id >='70';
> +----+---------------------+---------------+------------+--------------------+--------+--------+--------+
> | id | created_at          | version       | project_id |
> parent_snapshot_id | status | purged | islast |
> +----+---------------------+---------------+------------+--------------------+--------+--------+--------+
> | 70 | 2008-03-03 14:44:33 | 4.0-SNAPSHOT  |         70 |
> NULL | P      |      0 |      1 |
> | 71 | 2008-03-03 17:10:45 | 4.0-SNAPSHOT  |         70 |
> NULL | C      |      0 |      0 |
> | 72 | 2008-03-04 09:25:09 | 4.0-SNAPSHOT  |         70 |
> NULL | T      |      0 |      0 |
> | 73 | 2008-03-04 10:04:43 | 4.0-SNAPSHOT  |         70 |
> NULL | T      |      0 |      0 |
> | 74 | 2008-03-04 11:44:48 | 4.0-SNAPSHOT  |         70 |
> NULL | T      |      0 |      0 |
> | 75 | 2008-03-04 12:02:52 | 3.11-SNAPSHOT |          1 |
> NULL | T      |      0 |      0 |
> +----+---------------------+---------------+------------+--------------------+--------+--------+--------+
>
> Regards,
> Andrew
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

--
Simon Brandhof, [phone]
Hortis, Consulting & Innovation team
Sonar , Open Source Quality Dashboard for Java projects
http://sonar.hortis.ch

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Andrew Prentice]

Hi Simon,
log attached, but the builds have been purged automatically. What's the timer on this? 24hrs?

Regards,
Andrew

Simon Brandhof wrote:

Hi Andrew,

Could you please attach the server logs ?

- stop the server
- delete the files logs/*
- edit conf/logback.xml and set the INFO level :
  <root>
    <level value="INFO"/>
    <appender-ref ref="SONAR_FILE"/>
  </root>
- restart the server
- wait a few minutes and logs are ready !

Thank you
Simon

On Tue, Mar 4, 2008 at 3:15 AM, Andrew Prentice [hidden email] wrote:
  

Several builds of a single project (Project A) triggered by one of our
CI servers have failed (due to java.lang.OutOfMemoryError: Java heap space)

The Sonar project/list dashboard states
"Currently analysing *Project A* (for about 19 hours), *Project A* (for
about 3 hours), *Project A* (for about 2 hours), *Project A* (for 36
minutes), and *Project B* (for 18 minutes)"

The Project B build did not fail but it appears its analysis is being
prevented by the previous Project A builds.  Is there a recommended way
for stopping the analysis of failed builds as restarting the server does
not do this?

I'm running Sonar 1.1 with MySQL 5.0.51a on OSX 10.5.1

FYI - snapshot_id for builds listed above are 71-75
mysql> select * from snapshots
   -> where id >='70';
+----+---------------------+---------------+------------+--------------------+--------+--------+--------+
| id | created_at          | version       | project_id |
parent_snapshot_id | status | purged | islast |
+----+---------------------+---------------+------------+--------------------+--------+--------+--------+
| 70 | 2008-03-03 14:44:33 | 4.0-SNAPSHOT  |         70 |
NULL | P      |      0 |      1 |
| 71 | 2008-03-03 17:10:45 | 4.0-SNAPSHOT  |         70 |
NULL | C      |      0 |      0 |
| 72 | 2008-03-04 09:25:09 | 4.0-SNAPSHOT  |         70 |
NULL | T      |      0 |      0 |
| 73 | 2008-03-04 10:04:43 | 4.0-SNAPSHOT  |         70 |
NULL | T      |      0 |      0 |
| 74 | 2008-03-04 11:44:48 | 4.0-SNAPSHOT  |         70 |
NULL | T      |      0 |      0 |
| 75 | 2008-03-04 12:02:52 | 3.11-SNAPSHOT |          1 |
NULL | T      |      0 |      0 |
+----+---------------------+---------------+------------+--------------------+--------+--------+--------+

Regards,
Andrew

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email



    

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Cédric Munger-2]

Hi,

The "timed out" projects since 12 hours are normally deleted, the task is fired at server startup and then each 2 hours.
Strange, in your case some projects were timed out since 19 hours.
Your logs look ok. We'll try to make things better to avoid this confusion with "timed out" projects

Thanks

On Wed, Mar 5, 2008 at 7:50 AM, Andrew Prentice <[hidden email]> wrote:

Hi Simon,
log attached, but the builds have been purged automatically. What's the timer on this? 24hrs?

Regards,
Andrew

Simon Brandhof wrote:

Hi Andrew,

Could you please attach the server logs ?

- stop the server
- delete the files logs/*
- edit conf/logback.xml and set the INFO level :
  <root>
    <level value="INFO"/>
    <appender-ref ref="SONAR_FILE"/>
  </root>
- restart the server
- wait a few minutes and logs are ready !

Thank you
Simon

On Tue, Mar 4, 2008 at 3:15 AM, Andrew Prentice [hidden email] wrote:
  

Several builds of a single project (Project A) triggered by one of our
CI servers have failed (due to java.lang.OutOfMemoryError: Java heap space)

The Sonar project/list dashboard states
"Currently analysing *Project A* (for about 19 hours), *Project A* (for
about 3 hours), *Project A* (for about 2 hours), *Project A* (for 36
minutes), and *Project B* (for 18 minutes)"

The Project B build did not fail but it appears its analysis is being
prevented by the previous Project A builds.  Is there a recommended way
for stopping the analysis of failed builds as restarting the server does
not do this?

I'm running Sonar 1.1 with MySQL 5.0.51a on OSX 10.5.1

FYI - snapshot_id for builds listed above are 71-75
mysql> select * from snapshots
   -> where id >='70';
+----+---------------------+---------------+------------+--------------------+--------+--------+--------+
| id | created_at          | version       | project_id |
parent_snapshot_id | status | purged | islast |
+----+---------------------+---------------+------------+--------------------+--------+--------+--------+
| 70 | 2008-03-03 14:44:33 | 4.0-SNAPSHOT  |         70 |
NULL | P      |      0 |      1 |
| 71 | 2008-03-03 17:10:45 | 4.0-SNAPSHOT  |         70 |
NULL | C      |      0 |      0 |
| 72 | 2008-03-04 09:25:09 | 4.0-SNAPSHOT  |         70 |
NULL | T      |      0 |      0 |
| 73 | 2008-03-04 10:04:43 | 4.0-SNAPSHOT  |         70 |
NULL | T      |      0 |      0 |
| 74 | 2008-03-04 11:44:48 | 4.0-SNAPSHOT  |         70 |
NULL | T      |      0 |      0 |
| 75 | 2008-03-04 12:02:52 | 3.11-SNAPSHOT |          1 |
NULL | T      |      0 |      0 |
+----+---------------------+---------------+------------+--------------------+--------+--------+--------+

Regards,
Andrew

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email



    

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email