Stages & jobs

  1. Build and Test

  2. Deploy

  3. Release

    Requires a user to start manually

Build result summary

Details

Completed
Duration
22 minutes
Labels
None
Revisions
openmrs-core
d148b6740412e23cabaee827ad02d8b6a8030b6e d148b6740412e23cabaee827ad02d8b6a8030b6e
openmrs-standalone
a007b20569b3776ca375346af549436b53296a95 a007b20569b3776ca375346af549436b53296a95
Release scripts
bb61e06483cd415a55b72cceac8d10ad00ee4e8a bb61e06483cd415a55b72cceac8d10ad00ee4e8a
Total tests
3570
Fixed in
#1579 (Manual run by Darius Jazayeri)
No failed test found. A possible compilation error occurred.

Tests

Responsible

  • djazayeri djazayeri Automatically assigned

Code commits

openmrs-core
Author Commit Message Commit date
Darius Jazayeri <jazayeri@alum.mit.edu> Darius Jazayeri <jazayeri@alum.mit.edu> d148b6740412e23cabaee827ad02d8b6a8030b6e d148b6740412e23cabaee827ad02d8b6a8030b6e TRUNK-4976 - Automatically set status to AMENDED when editing a FINAL obs

Jira issues

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

Error summary for Build and Test

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

INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Successfully released change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 4/8/17 12:08 AM:liquibase: Successfully acquired change log lock
INFO 4/8/17 12:08 AM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 4/8/17 12:08 AM: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 4/8/17 12:09 AM: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.