Sonar metrics for OpenMRS Core Master

Build: #1013 failed Scheduled with changes by 5 people

Build result summary

Details

Completed
Duration
12 minutes
Labels
None
Revision
b95519d9fd1e5efa34983a700548474cd47313cb b95519d9fd1e5efa34983a700548474cd47313cb
Total tests
3346
Fixed in
#1015 (Scheduled)
No failed test found. A possible compilation error occurred.

Tests

Responsible

Code commits

Author Commit Message Commit date
bharatak <bharatak@thoughtworks.com> bharatak <bharatak@thoughtworks.com> b95519d9fd1e5efa34983a700548474cd47313cb b95519d9fd1e5efa34983a700548474cd47313cb Dirty Flag should not be set for new obs
Wyclif Luyima Wyclif Luyima 212bef82962382bcd7df2181e5a0a29cb70fa7e7 212bef82962382bcd7df2181e5a0a29cb70fa7e7 Follow up to clean up javadocs for ModuleUtil.isOpenmrsVersionInVersions - TRUNK-4941
Wyclif Luyima Wyclif Luyima 0078b29842858b8c5d4229f195d28b721adcfc2f 0078b29842858b8c5d4229f195d28b721adcfc2f Merge pull request #1836 from teleivo/TRUNK-4941
Add ModuleUtil.isOpenmrsVersionInVersions() - TRUNK-4941
Rafal Korytkowski Rafal Korytkowski d663ec3a6010281ab5ffcba98a56d4a691d7749e d663ec3a6010281ab5ffcba98a56d4a691d7749e TRUNK-4943 Follow up
Daniel Kayiwa Daniel Kayiwa a93de48980f101b3168efc004d1602b161da978f a93de48980f101b3168efc004d1602b161da978f Merge pull request #1838 from teleivo/javadoc-compareversion
Clarify ModuleUtil javadoc of matching version methods

Jira issues

IssueDescriptionStatus
Unknown Issue TypeTRUNK-4941Could not obtain issue details from Jira
Unknown Issue TypeTRUNK-4943Could not obtain issue details from Jira

Error summary for Sonar Full Analysis

The job generated some errors, drill down into the full build log for more details.

INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Successfully released change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 9/19/16 9:01 PM:liquibase: Successfully acquired change log lock
INFO 9/19/16 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 9/19/16 9:01 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 9/19/16 9:02 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.