No resuls of Code Inspection on build 3989

Hello,

Your logs contain errors from Ipr runner which can be caused by upgrade from
HSQLDB to MySQL.

"No data recorded for Inspections" error was fixed for Beta. Try build 4037
please.

Thank you.

-

Anna Kozlova
JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

I'm trying to setup the Code Inspection on build 3989 but without
success.

These are the properties defined in buildAgent.properties file on the
build agent:

global.library.sso.path=../libraries/sso
global.library.wasp.path=../libraries/wasp
global.library.JBoss4.path=../jboss-4.0.5.GA
system.jdk.1.4.home=c\:
jdk1.4
The log contains these errors:
Checking project...
: Error : JBoss4 - Library is referenced,
but not defined
: Container where it's expected to find the
library:
: - Global
: Error : wasp - Library is referenced, but
not defined
: Container where it's expected to find the
library:
: - Global
Also it contains many of these messages (although the directories do
exist):

: Warning:
c:/TeamCity/buildAgent/work/Server/Apollo2/build-project/apollo2sc/../
../registry/components/application_core/src - Source root doesn't
exist

: Warning:
c:/TeamCity/buildAgent/work/Server/Apollo2/build-project/apollo2sc/../
../debug/src - Source root doesn't exist

: Warning:
c:/TeamCity/buildAgent/work/Server/Apollo2/build-project/apollo2sc/../
../debug/test - Source root doesn't exist

It contains many other errors and finaly this:
BUILD FAILED
c:\TeamCity\buildAgent\work\Server\Apollo2\integrationBuild.xml:1894:
c:\TeamCity\buildAgent\work\Server\Apollo2\%global.library.JBoss4.path
% not found.
Whole inspections take more than 2 hours, here is the end of the log:

: Analyzing code... 85%
: Analyzing code... 86%
: Done.
: Build has too many problems ...
: updating diff...
And after all that, these are the results:

Code inspection
No data recorded.

Your logs contain errors from Ipr runner which can be
caused by upgrade from
HSQLDB to MySQL.

I have never used MySQL with TC. What do you mean by the upgrade?

"No data recorded for Inspections" error was fixed
for Beta. Try build 4037
please.

I reinstalled TC and I'm using build 4037 but still, every second inspection contains no data, this is the result:
Code inspection
No data recorded.

Funny, when comparing two logs of two inspections (with and without recorded data), I can see no apparent difference. These are the Build Log ends of two subsequent Inspections (first successful, second no data recorded):
...
: Analyzing code... 86%
: Done.
: Build has too many problems ...
: updating diff...
: Total: 26042 (6 -3) Errors: 438 (0 -0)
: Inspection output:
...

: Analyzing code... 86%
: Done.
: Build has too many problems ...
: updating diff...
: Inspection output:
...

Since of this behaviour, I can't use TC in production - it is too unreliable.

Hello,

>> Your logs contain errors from Ipr runner which can be
>> caused by upgrade from
>> HSQLDB to MySQL.

I have never used MySQL with TC. What do you mean by the upgrade?

Then you just send us messages from the log from your .ipr build and not
from inspections build. Could you please send full teamcity.log and errors.log
from agent as well as idea.log from PROJECT_WORKING_DIR/system/idea.log and
your .ipr file.

Did you try inspections in Agara? When did they end with some results last
time?

Thank you

>> "No data recorded for Inspections" error was fixed
>> for Beta. Try build 4037
>> please.

I reinstalled TC and I'm using build 4037 but still, every second
inspection contains no data, this is the result:

Code inspection

No data recorded.

Funny, when comparing two logs of two inspections (with and without
recorded data), I can see no apparent difference. These are the Build
Log ends of two subsequent Inspections (first successful, second no
data recorded):

..

: Analyzing code... 86%

: Done.

: Build has too many problems ...

: updating diff...

: Total: 26042 (6 -3) Errors: 438 (0 -0)

: Inspection output:

..

: Analyzing code... 86%
: Done.
: Build has too many problems ...
: updating diff...
: Inspection output:
..
Since of this behaviour, I can't use TC in production - it is too
unreliable.