Sonar metrics for OpenMRS Core Master

Build: #1191 failed Scheduled with changes by SwathiVarkala <swathivarkala@gmail.com>

Build result summary

Details

Completed
Duration
18 minutes
Labels
None
Revision
ce7772d59b091f17c26c6a40cc930bf779a528d7 ce7772d59b091f17c26c6a40cc930bf779a528d7
Total tests
3462
Failing since
#1182 (Scheduled with changes by Darius Jazayeri <jazayeri@alum.mit.edu>)
Fixed in
#1194 (Manual run by Cintia Del Rio)
No failed test found. A possible compilation error occurred.

Tests

Responsible

  • djazayeri djazayeri Automatically assigned

Code commits

Author Commit Message Commit date
SwathiVarkala <swathivarkala@gmail.com> SwathiVarkala <swathivarkala@gmail.com> ce7772d59b091f17c26c6a40cc930bf779a528d7 ce7772d59b091f17c26c6a40cc930bf779a528d7 TRUNK-5109 Added getRevisionObs on obsService
(cherry picked from commit 21225c255023f91c68b7466b1cdd6779fba7b598)

Configuration changes

Plan configuration has changed since the last successful build. See the plan audit log for more details.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeTRUNK-5109Could 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 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Successfully released change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 9:01 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/12/17 9:01 PM:liquibase: Successfully acquired change log lock
INFO 3/12/17 9:01 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/12/17 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-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 3/12/17 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-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.
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException