Log file for SONAR-3232

[Yves Langisch-2]

Please find attached the log file.

-
Yves


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

    http://xircles.codehaus.org/manage_email

[Freddy Mallet]

Hi Yves,

According to your last comment on SONAR-3231 ticket, this failure is due to some parallel analysis on the same Sonar project and this is a known Sonar limitation.

See http://jira.codehaus.org/browse/SONAR-3306 and http://jira.codehaus.org/browse/SONAR-2761. 

Kind regards,

Freddy

-----

twitter.com/FreddyMallet

Sonar for Continuous Inspection

On Thu, Jun 28, 2012 at 9:59 AM, Yves Langisch <[hidden email]> wrote:

Please find attached the log file.

-
Yves


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

    http://xircles.codehaus.org/manage_email

[Yves Langisch-2]

Hi Freddy,

Just rechecked our nightly jobs. Of course there are parallel sonar
analysis as we have a few hundreds CI jobs but these are all different
projects with different name/artifactId. They have the same parent pom
though which must not be a problem.

I'm pretty positive that we do not have parallel runs of the same project.

Any other known use case that can cause this problem?

Regards,
Yves

On 02.07.2012 21:55, Freddy Mallet wrote:

> Hi Yves,
>
> According to your last comment on SONAR-3231 ticket, this failure is due
> to some parallel analysis on the same Sonar project and this is a known
> Sonar limitation.
>
> See http://jira.codehaus.org/browse/SONAR-3306 and
> http://jira.codehaus.org/browse/SONAR-2761.
>
> Kind regards,
> Freddy
>
> -----
> twitter.com/FreddyMallet <https://twitter.com/FreddyMallet>
> Sonar for Continuous Inspection
>
>
>
> On Thu, Jun 28, 2012 at 9:59 AM, Yves Langisch <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Please find attached the log file.
>
>     -
>     Yves
>
>
>     ---------------------------------------------------------------------
>     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

[Freddy Mallet]

Hi Yves, 

I'm sorry to come back with the same explanation but each time this issue was encountered this was always for the same reason : parallel analysis on the same project or ... on a project and on one of its module.

Let's take a simple example : project A contains module AA and module AB.

If at the same time project AA and module AA are analysed (whatever is the reason), this error can also occur. 

Kind regards,

Freddy

-----

twitter.com/FreddyMallet

Sonar for Continuous Inspection

On Thu, Jul 5, 2012 at 8:16 AM, Yves Langisch <[hidden email]> wrote:

Hi Freddy,

Just rechecked our nightly jobs. Of course there are parallel sonar analysis as we have a few hundreds CI jobs but these are all different projects with different name/artifactId. They have the same parent pom though which must not be a problem.

I'm pretty positive that we do not have parallel runs of the same project.

Any other known use case that can cause this problem?

Regards,
Yves

On 02.07.2012 21:55, Freddy Mallet wrote:

Hi Yves,

According to your last comment on SONAR-3231 ticket, this failure is due
to some parallel analysis on the same Sonar project and this is a known
Sonar limitation.

See http://jira.codehaus.org/browse/SONAR-3306 and
http://jira.codehaus.org/browse/SONAR-2761.

Kind regards,
Freddy

-----

twitter.com/FreddyMallet <https://twitter.com/FreddyMallet>

Sonar for Continuous Inspection



On Thu, Jun 28, 2012 at 9:59 AM, Yves Langisch <[hidden email]

<mailto:[hidden email]>> wrote:

    Please find attached the log file.

    -
    Yves


    ---------------------------------------------------------------------
    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