Sonar metrics for OpenMRS Core Master
Build: #1210 failed
Job: Sonar Full Analysis failed
Job result summary
- Completed
- Duration
- 87 minutes
- Revision
-
45d9d3374bbbb66fdf84ad5498a2e0566cc6f4c9
45d9d3374bbbb66fdf84ad5498a2e0566cc6f4c9 - Total tests
- 3452
- Fixed in
- #1211 (Manual run by Daniel Kayiwa)
Tests
- 3,452 tests in total
- 3 tests failed
- 3 failures are new
- 38 tests were quarantined / skipped
- 64 minutes taken in total.
Status | Test | Duration | |
---|---|---|---|
Collapse |
ReflectTest
getAllFields_shouldReturnAllFieldsIncludePrivateAndSuperClasses
|
< 1 sec | |
java.lang.IllegalArgumentException: Field not found! at org.openmrs.util.ReflectTest.findFieldByName(ReflectTest.java:62) at org.openmrs.util.ReflectTest.getAllFields_shouldReturnAllFieldsIncludePrivateAndSuperClasses(ReflectTest.java:74) |
|||
Collapse |
ReflectTest
getInheritedFields_shouldReturnOnlyTheSubClassFieldsOfGivenParameterizedClass
|
< 1 sec | |
java.lang.IllegalArgumentException: Field not found! at org.openmrs.util.ReflectTest.findFieldByName(ReflectTest.java:62) at org.openmrs.util.ReflectTest.getInheritedFields_shouldReturnOnlyTheSubClassFieldsOfGivenParameterizedClass(ReflectTest.java:133) |
|||
Collapse |
ReflectTest
isCollection_shouldReturnFalseIfGivenFieldClassIsNotACollectionClass
|
< 1 sec | |
java.lang.IllegalArgumentException: Field not found! at org.openmrs.util.ReflectTest.findFieldByName(ReflectTest.java:62) at org.openmrs.util.ReflectTest.isCollection_shouldReturnFalseIfGivenFieldClassIsNotACollectionClass(ReflectTest.java:86) |
Error summary
The build generated some errors. See the full build log for more details.
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 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/29/17 9:14 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.
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Successfully released change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/29/17 9:12 PM:liquibase: Successfully acquired change log lock
INFO 3/29/17 9:12 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/29/17 9:12 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/29/17 9:14 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.