Sonar metrics for OpenMRS Core Master

Build: #1211 was successful

Job: Sonar Full Analysis was successful

Stages & jobs

  1. Sonar Analysis

Job result summary

Completed
Duration
42 minutes
Revision
363d0e25e807b4a92f78bb158ff52a34fce6a618 363d0e25e807b4a92f78bb158ff52a34fce6a618
Total tests
3483
First to pass since
#1210 (Scheduled – )

Tests

  • 3,483 tests in total
  • 3 tests were fixed
  • 40 tests were quarantined / skipped
  • 16 minutes taken in total.
Fixed tests 3
Status Test Failing since Duration
Successful ReflectTest getAllFields_shouldReturnAllFieldsIncludePrivateAndSuperClasses History
Failing since build #1210 (Scheduled) < 1 sec
Successful ReflectTest getInheritedFields_shouldReturnOnlyTheSubClassFieldsOfGivenParameterizedClass History
Failing since build #1210 (Scheduled) < 1 sec
Successful ReflectTest isCollection_shouldReturnFalseIfGivenFieldClassIsNotACollectionClass History
Failing since build #1210 (Scheduled) < 1 sec

Error summary

The build generated some errors. See the full build log for more details.

INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/30/17 1:31 PM:liquibase: Successfully acquired change log lock
INFO 3/30/17 1:31 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/30/17 1:31 PM:liquibase: Successfully released change log lock
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/bamboo-agent-1/.m2/repository/org/slf4j/slf4j-log4j12/1.6.0/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/bamboo-agent-1/.m2/repository/org/slf4j/slf4j-log4j12/1.6.0/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
INFO 3/30/17 1:32 PM:liquibase: Reading from LIQUIBASECHANGELOG
[Field error in object 'term' on field 'conceptReferenceTermMaps[1].termB': rejected value [weight term(WGT234)]; codes [ConceptReferenceTerm.termToTerm.alreadyMapped.term.conceptReferenceTermMaps[1].termB,ConceptReferenceTerm.termToTerm.alreadyMapped.term.conceptReferenceTermMaps.termB,ConceptReferenceTerm.termToTerm.alreadyMapped.conceptReferenceTermMaps[1].termB,ConceptReferenceTerm.termToTerm.alreadyMapped.conceptReferenceTermMaps.termB,ConceptReferenceTerm.termToTerm.alreadyMapped.termB,ConceptReferenceTerm.termToTerm.alreadyMapped.org.openmrs.ConceptReferenceTerm,ConceptReferenceTerm.termToTerm.alreadyMapped]; arguments []; default message [Cannot map a reference term multiple times to the same concept reference term]]
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/bamboo-agent-1/.m2/repository/org/slf4j/slf4j-log4j12/1.6.0/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/bamboo-agent-1/.m2/repository/org/slf4j/slf4j-log4j12/1.6.0/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/bamboo-agent-1/.m2/repository/org/slf4j/slf4j-log4j12/1.6.0/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/home/bamboo-agent-1/.m2/repository/org/slf4j/slf4j-log4j12/1.6.0/slf4j-log4j12-1.6.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.