Build: #1566 failed

Job: Build and Test failed

Stages & jobs

  1. Build and Test

  2. Deploy

  3. Release

    Requires a user to start manually

Job result summary

Completed
Duration
15 minutes
Revision
88b8255073ba16c1072403462f4736134c3b23c9 88b8255073ba16c1072403462f4736134c3b23c9
Total tests
3476
Fixed in
#1568 (Code changes detected)

Tests

  • 3,476 tests in total
  • 1 test failed
  • 1 failure is new
  • 37 tests were quarantined / skipped
  • 11 minutes taken in total.
New test failures 1
Status Test Duration
Collapse Failed ConceptValidatorTest validate_shouldFailIfAnyNameIsAnEmptyString History
< 1 sec
java.lang.AssertionError: 
Expected: to have global error of code 'Concept.name.empty'
     but: was <org.springframework.validation.BindException: org.springframework.validation.BeanPropertyBindingResult: 2 errors
Field error in object 'concept' on field 'datatype': rejected value [null]; codes [Concept.datatype.empty.concept.datatype,Concept.datatype.empty.datatype,Concept.datatype.empty.org.openmrs.ConceptDatatype,Concept.datatype.empty]; arguments []; default message [null]
Field error in object 'concept' on field 'conceptClass': rejected value [null]; codes [Concept.conceptClass.empty.concept.conceptClass,Concept.conceptClass.empty.conceptClass,Concept.conceptClass.empty.org.openmrs.ConceptClass,Concept.conceptClass.empty]; arguments []; default message [null]>
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:8)
	at org.openmrs.validator.ConceptValidatorTest.validate_shouldFailIfAnyNameIsAnEmptyString(ConceptValidatorTest.java:85)

Error summary

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

INFO 3/31/17 5:10 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:10 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:10 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:10 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:10 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:10 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:10 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:10 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:10 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:10 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:10 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:10 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:10 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:10 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:10 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Successfully released change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 PM:liquibase: Reading from LIQUIBASECHANGELOG
INFO 3/31/17 5:11 PM:liquibase: Successfully acquired change log lock
INFO 3/31/17 5:11 PM:liquibase: liquibase.xml is using schema version 1.9 rather than version 2.0
INFO 3/31/17 5:11 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/31/17 5:11 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.