Sonar metrics for OpenMRS Core Master

Build: #1018 was successful

Job: Sonar Full Analysis was successful

Stages & jobs

  1. Sonar Analysis

Job result summary

Completed
Duration
19 minutes
Revision
6472b66b69336657e7ff31f0487badd379a2afcf 6472b66b69336657e7ff31f0487badd379a2afcf
Total tests
3347
First to pass since
#1016 (Scheduled – )

Tests

  • 3,347 tests in total
  • 39 tests were quarantined / skipped
  • 4 minutes taken in total.

Error summary

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

INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/22/16 3:33 PM:liquibase: Successfully acquired change log lock
INFO 9/22/16 3:33 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/22/16 3:33 PM:liquibase: Successfully released change log lock
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/home/bamboo-agent-2/.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-2/.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 9/22/16 3:34 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-2/.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-2/.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-2/.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-2/.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.